Libraries tagged by accounts
solwin/cancelorder
7 Downloads
The Magento 2 Cancel Order By Customer extension allows user to cancel the order from front end. Now customer can easily cancel or delete the order from my account or dashboard page.
solomon-ochepa/nuban
141 Downloads
You can use it to get the account name of any bank account in Nigeria
smartymedia/hide-downloadable
1 Downloads
A Magento 2.2 module to add "Is Visible" attribute to Downloadable products' links. Hides links on "My Downloadable Products" account view page if "Is Visible" set to "No" for that link
slackero/php-iban
3 Downloads
php-iban is a library for parsing and validating IBAN (and IIBAN) bank account information.
skrish/novalnet-skrish-module
4 Downloads
This display the coupon list in my account page
skowalsky/guestorder
5 Downloads
Extends MERCONIS order functionality to differ between private and business customers, when the customer has no user account
sitewards/extendedaccountnavigation
2448 Downloads
Extended Customer Account Navigation
sintexph/acms-lib
6 Downloads
A library that will sync accounts from acms
shophy/wechat
3 Downloads
WeChat Official Accounts SDK
shongpon/yii2-eauth-ega-th
1 Downloads
Yii2 EAuth Extension. EAuth allows to authenticate users with accounts on other websites (Google, Facebook, Twitter, etc).
sentdm/whats-app-business-management-api
6 Downloads
The WhatsApp Business Management API allows you to programmatically manage your WhatsApp Business Account assets, such as message templates and phone numbers.
segnivo/php-sdk
0 Downloads
**API Version**: 1.7 **Date**: 9th July, 2024 ## 📄 Getting Started This API is based on the REST API architecture, allowing the user to easily manage their data with this resource-based approach. Every API call is established on which specific request type (GET, POST, PUT, DELETE) will be used. The API must not be abused and should be used within acceptable limits. To start using this API, you will need not create or access an existing Segnivo account to obtain your API key ([retrievable from your account settings](https://messaging.segnivo.com/account/api)). - You must use a valid API Key to send requests to the API endpoints. - The API only responds to HTTPS-secured communications. Any requests sent via HTTP return an HTTP 301 redirect to the corresponding HTTPS resources. - The API returns request responses in JSON format. When an API request returns an error, it is sent in the JSON response as an error key or with details in the message key. ### 🔖 **Need some help?** In case you have questions or need clarity with interacting with some endpoints feel free to create a support ticket on your account or you can send an email ([[email protected]](https://mailto:[email protected])) directly and we would be happy to help. --- ## Authentication As noted earlier, this API uses API keys for authentication. You can generate a Segnivo API key in the [API](https://messaging.segnivo.com/account/api) section of your account settings. You must include an API key in each request to this API with the `X-API-KEY` request header. ### Authentication error response If an API key is missing, malformed, or invalid, you will receive an HTTP 401 Unauthorized response code. ## Rate and usage limits API access rate limits apply on a per-API endpoint basis in unit time. The limit is 10k requests per hour for most endpoints and 1m requests per hour for transactional/relay email-sending endpoints. Also, depending on your plan, you may have usage limits. If you exceed either limit, your request will return an HTTP 429 Too Many Requests status code or HTTP 403 if sending credits have been exhausted. ### 503 response An HTTP `503` response from our servers may indicate there is an unexpected spike in API access traffic, while this rarely happens, we ensure the server is usually operational within the next two to five minutes. If the outage persists or you receive any other form of an HTTP `5XX` error, contact support ([[email protected]](https://mailto:[email protected])). ### Request headers To make a successful request, some or all of the following headers must be passed with the request. | **Header** | **Description** | | --- | --- | | Content-Type | Required and should be `application/json` in most cases. | | Accept | Required and should be `application/json` in most cases | | Content-Length | Required for `POST`, `PATCH`, and `PUT` requests containing a request body. The value must be the number of bytes rather than the number of characters in the request body. | | X-API-KEY | Required. Specifies the API key used for authorization. | ##### 🔖 Note with example requests and code snippets If/when you use the code snippets used as example requests, remember to calculate and add the `Content-Length` header. Some request libraries, frameworks, and tools automatically add this header for you while a few do not. Kindly check and ensure yours does or add it yourself.
sdrockdev/laravel-newsletters
1947 Downloads
Manage newsletters in Laravel (for multiple accounts)
sdksio/pnz-payments-sdk
2 Downloads
PNZ Payments Account and Transaction API
scheibo/steamsso
5 Downloads
A Steam SSO plugin for seamless integration with Steam accounts in Kirby, enabling users to log in with their Steam credentials. Simplifies authentication for gaming platforms and services.