The Glomo API follows REST architecture, utilizing resource-oriented URLs for clarity. It handles form-encoded request bodies, delivers responses in JSON format, and operates with standard HTTP methods, authentication, and response codes.
You can download the complete API collection by using the download options on the right.
https://api.glomopay.com/api/v1/
The unique identifier for the bank account validation.
The status of the bank account validation. This does not mean the bank account is valid or invalid. It means the validation process was successful or failed.
The message returned by the bank account validation process.
{ "id": "aval_5JU9yv0lGSUP", "status": "success", "validation_message": "The account is registered to John Doe", "fee_charged": { "amount": 1000, "currency": "USD" } }
The country where the customer is located. Country should be sent as a ISO 3166-1 alpha-3 code.
The account number of the bank account as provided by the bank.
The primary BIC of the bank account. This is the BIC of the bank where the account is held. This is also known as the SWIFT code.
https://api.glomopay.com/api/v1/bank_account_validation
curl -i -X POST \
https://api.glomopay.com/api/v1/bank_account_validation \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"country": "Ind",
"holder_name": "John Doe",
"account_number": "987654321001",
"bic_primary": "QWERIN000",
"bic_secondary": "YESB0000002"
}'Bank account validation successful
The unique identifier for the bank account validation.
The status of the bank account validation. This does not mean the bank account is valid or invalid. It means the validation process was successful or failed.
The message returned by the bank account validation process.
{ "id": "aval_5JU9yv0lGSUP", "status": "success", "validation_message": "The account is registered to John Doe", "fee_charged": { "amount": 1000, "currency": "USD" } }
The ID of the beneficiary bank account to filter validations
The ISO 3166-1 alpha-3 code of the country to filter validations
ISO-8601 timestamp in UTC to filter resources created before this time. Use this to avoid Page drift issue. See Pagination parameters for more details.
ISO-8601 timestamp in UTC to filter resources created after this time. Use this to avoid Page drift issue. See Pagination parameters for more details.
https://api.glomopay.com/api/v1/bank_account_validation
curl -i -X GET \
'https://api.glomopay.com/api/v1/bank_account_validation?beneficiary_account_id=bene_5JU9yv0lGSUP&country=Ind&before=2025-02-18T12%3A03%3A44Z&after=2025-01-18T12%3A03%3A44Z&per_page=20&page=1' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{ "data": [ { … } ], "page_meta": { "current": 2, "previous": 1, "next": 3, "per_page": 20, "pages": 10, "count": 200 } }
This resource represents internal fund movements between merchant accounts within the platform–partner model. Internal transfers enable seamless fund movement between merchants who operate under the same platform account. Internal transfers are restricted to accounts linked under the same platform hierarchy. The following transfer directions are supported:
| Transfer Type | Description |
|---|---|
| P → C | From a Platform (P) account to one of its Child (C) merchant accounts. |
| C → P | From a Child (C) merchant account back to its Platform (P) account. |
| C → C (same P) | Between Child (C) accounts under the same Platform (P). |