Skip to content

API specification for Glomo (1.0.0)

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.

Download OpenAPI description
Languages
Servers
Production server
https://api.glomopay.com/api/v1

This resource represents your Glomo balance. You can retrieve it to see the current balance on your Glomo account in all currencies enabled for your account.

Schemas
Operations

Balance Conversion resource represents the details of the balance conversion. The balance conversion is the conversion of the balance from one supported currency to another supported currency.

Schemas
Operations

This resource represents the order details. The order is the request to receive payment from your customer.

Schemas
Operations

This resource represents a customer of your business. The customer can be an individual or a business from whom you will receive payments.

Schemas
Operations

This resource represents a payment attempt made by your customer. The payment can either be successfully completed or failed, depending on various factors.

Schemas
Operations

This resource represents a refund transaction from your Glomo account to your customer. You can retrieve it to see the details of the refund transaction.

Schemas
Operations

This resource represents the details of the referral fees to be configured at the order or payment link level. Only platform businesses are allowed to create prices. The first Price created is set as default for a business.

Schemas
Operations

This resource represents a recurring billing agreement for a customer. Subscriptions allow businesses to automatically charge customers on a regular schedule according to a defined billing plan.

Schemas
Operations

This resource represents the disbursement transactions from your Glomo account to your beneficiaries.

Schemas
Operations

This resource represents a payee of a payout initiated by your business. The beneficiary can be an individual or a business to whom you will send funds.

Schemas
Operations

This resource represents a payee of a payout initiated by your business. Beneficiary V2 introduces a structured nested format for beneficiary, address, and bank account details, and supports both bank account and UPI payment methods.

Schemas
Operations
idstringread-only

The unique identifier for the beneficiary.

Example: "ben_5JU9yv0lGSUP"
namestring

The name of the beneficiary.

Example: "ACME Corporation"
typestring

The type of beneficiary. Defaults to "business" if not provided.

Enum"individual""business"
Example: "business"
categorystringread-only

The category of the beneficiary.

Enum"lrs""payout"
Example: "lrs"
emailstring(email)

The email address of the beneficiary.

Example: "finance@acme.com"
phonestring

The phone number of the beneficiary.

Example: "+1-555-123-4567"
nicknamestring

A nickname for the beneficiary. If not provided, auto-generated as "{beneficiary_name} - {bank_name}".

Example: "ACME Primary Account"
addressobject

The address of the beneficiary.

bank_accountobject

The bank account details of the beneficiary.

statusstringread-only

The current review status of the beneficiary.

Enum"pending""active""rejected"
Example: "pending"
documentsArray of stringsread-only

List of document IDs attached to the beneficiary.

Example: ["doc_68e7980auYRAs"]
upi_accountobject or null

The UPI account details of the beneficiary. Present when the beneficiary uses UPI, otherwise null.

created_atstring(date-time)read-only

Timestamp representing when the beneficiary was created in ISO 8601 format.

Example: "2025-01-15T10:00:00Z"
updated_atstring(date-time)read-only

Timestamp representing when the beneficiary was last updated in ISO 8601 format.

Example: "2025-01-15T10:00:00Z"
{ "id": "ben_5JU9yv0lGSUP", "name": "ACME Corporation", "type": "business", "category": "lrs", "email": "finance@acme.com", "phone": "+1-555-123-4567", "nickname": "ACME Primary Account", "address": { "address_line1": "123 Business Park", "address_line2": "Suite 100", "city": "New York", "state": "NY", "country_code": "USA", "postal_code": "10001" }, "bank_account": { "account_number": "1234567890", "name": "Citibank NA", "swift_code": "CITIUS33", "local_routing_number": "021000089", "currency": "USD", "address": { … }, "intermediate_bank": { … } }, "status": "pending", "documents": [ "doc_68e7980auYRAs" ], "upi_account": { "upi_id": "1111111111@ybl" }, "created_at": "2025-01-15T10:00:00Z", "updated_at": "2025-01-15T10:00:00Z" }

Request

Creates a beneficiary with structured nested objects for beneficiary details, address, and bank account or UPI information.

Security
JWT
Bodyapplication/jsonrequired
categorystringrequired

The category of the beneficiary. Use "lrs" for LRS (Liberalised Remittance Scheme) beneficiaries or "payout" for payout beneficiaries.

Enum"lrs""payout"
Example: "lrs"
beneficiaryobjectrequired

The beneficiary details including name, contact information, and address.

beneficiary.​namestringrequired

The name of the beneficiary. This is a required field.

Example: "ACME Corporation"
beneficiary.​typestring

The type of beneficiary. Defaults to "business" if not provided.

Default "business"
Enum"individual""business"
Example: "business"
beneficiary.​emailstring(email)

The email address of the beneficiary.

Example: "finance@acme.com"
beneficiary.​phonestring

The phone number of the beneficiary.

Example: "+1-555-123-4567"
beneficiary.​nicknamestring

A nickname for the beneficiary. If not provided, it will be auto-generated as "{beneficiary_name} - {bank_name}".

Example: "ACME Primary Account"
beneficiary.​addressobjectrequired

The address of the beneficiary. All fields except address_line2 are required.

beneficiary.​address.​address_line1stringrequired

The street address of the beneficiary (required).

Example: "123 Business Park"
beneficiary.​address.​address_line2string

The second line of street address of the beneficiary (optional).

Example: "Suite 100"
beneficiary.​address.​citystringrequired

The city where the beneficiary is located (required).

Example: "New York"
beneficiary.​address.​statestringrequired

The state or administrative area where the beneficiary is located (required).

Example: "NY"
beneficiary.​address.​country_codestring(iso-3166-1-alpha-3)required

The country where the beneficiary is located (required). Country should be sent as a ISO 3166-1 alpha-3 code.

Example: "USA"
beneficiary.​address.​postal_codestringrequired

The postal code of the beneficiary's address (required).

Example: "10001"
bank_accountobject

The bank account details of the beneficiary.

upi_accountobject

UPI account details. Provide either bank_account or upi_account, not both.

documentsArray of strings

Optional list of document IDs to attach to the beneficiary.

Example: ["doc_68e7980auYRAs"]
curl -i -X POST \
  https://api.glomopay.com/api/v2/beneficiaries \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "category": "lrs",
    "beneficiary": {
      "name": "ACME Corporation",
      "type": "business",
      "email": "finance@acme.com",
      "phone": "+1-555-123-4567",
      "nickname": "ACME Primary Account",
      "address": {
        "address_line1": "123 Business Park",
        "address_line2": "Suite 100",
        "city": "New York",
        "state": "NY",
        "country_code": "USA",
        "postal_code": "10001"
      }
    },
    "bank_account": {
      "account_number": "1234567890",
      "name": "Citibank NA",
      "swift_code": "CITIUS33",
      "local_routing_number": "021000089",
      "currency": "USD",
      "address": {
        "address_line1": "388 Greenwich Street",
        "city": "New York",
        "state": "NY",
        "country_code": "USA",
        "postal_code": "10013"
      },
      "intermediate_bank": {
        "name": "JPMorgan Chase Bank",
        "country": "USA",
        "swift_code": "CHASUS33",
        "account_number": "123456789"
      }
    }
  }'

Responses

Beneficiary created successfully

Bodyapplication/json
idstringread-only

The unique identifier for the beneficiary.

Example: "ben_5JU9yv0lGSUP"
namestring

The name of the beneficiary.

Example: "ACME Corporation"
typestring

The type of beneficiary. Defaults to "business" if not provided.

Enum"individual""business"
Example: "business"
categorystringread-only

The category of the beneficiary.

Enum"lrs""payout"
Example: "lrs"
emailstring(email)

The email address of the beneficiary.

Example: "finance@acme.com"
phonestring

The phone number of the beneficiary.

Example: "+1-555-123-4567"
nicknamestring

A nickname for the beneficiary. If not provided, auto-generated as "{beneficiary_name} - {bank_name}".

Example: "ACME Primary Account"
addressobject

The address of the beneficiary.

bank_accountobject

The bank account details of the beneficiary.

statusstringread-only

The current review status of the beneficiary.

Enum"pending""active""rejected"
Example: "pending"
documentsArray of stringsread-only

List of document IDs attached to the beneficiary.

Example: ["doc_68e7980auYRAs"]
upi_accountobject or null

The UPI account details of the beneficiary. Present when the beneficiary uses UPI, otherwise null.

created_atstring(date-time)read-only

Timestamp representing when the beneficiary was created in ISO 8601 format.

Example: "2025-01-15T10:00:00Z"
updated_atstring(date-time)read-only

Timestamp representing when the beneficiary was last updated in ISO 8601 format.

Example: "2025-01-15T10:00:00Z"
Response
application/json
{ "id": "bene_5JU9yv0lGSUP", "name": "ACME Corporation", "type": "business", "category": "lrs", "status": "pending", "email": "finance@acme.com", "phone": "+1-555-123-4567", "nickname": "ACME Primary Account", "upi_account": null, "created_at": "2025-01-15T10:00:00Z", "updated_at": "2025-01-15T10:00:00Z", "address": { "address_line1": "123 Business Park", "address_line2": "Suite 100", "city": "New York", "state": "NY", "country_code": "USA", "postal_code": "10001" }, "bank_account": { "account_number": "1234567890", "name": "Citibank NA", "swift_code": "CITIUS33", "local_routing_number": "021000089", "currency": "USD", "address": { … }, "intermediate_bank": { … } } }

Request

Returns a paginated list of beneficiaries. Optionally filter by status.

Security
JWT
Query
statusstring

Filter beneficiaries by status.

Enum"pending""active""rejected"
Example: status=active
pageinteger

Page number for pagination.

Example: page=1
per_pageinteger

Number of results per page.

Example: per_page=20
curl -i -X GET \
  'https://api.glomopay.com/api/v2/beneficiaries?status=active&page=1&per_page=20' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

A paginated list of beneficiaries

Bodyapplication/json
dataArray of objects(BeneficiaryV2)
page_metaobject
Response
application/json
{ "data": [ { … } ], "page_meta": { "current": 1, "previous": null, "next": null, "per_page": 20, "pages": 1, "count": 10 } }

Bank Account Validation resource represents the validation details of a bank account.

Schemas
Operations

Document resource represents the documents details uploaded. This document is used in payin, payout, etc.

Schemas
Operations

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 TypeDescription
P → CFrom a Platform (P) account to one of its Child (C) merchant accounts.
C → PFrom a Child (C) merchant account back to its Platform (P) account.
C → C (same P)Between Child (C) accounts under the same Platform (P).
Schemas
Operations

This resource represents the settlement details. The settlement is the process of transferring funds from your Glomo account to your bank account.

Schemas
Operations

This resource represents virtual account details. A virtual account is a unique account number provisioned for a customer, allowing payments to be received and transactions to be tracked against that customer.

Schemas
Operations

This resource provides platform functionality that enables platforms to onboard merchants onto Glomo, with each merchant having their own dedicated Virtual Accounts (VA).

Schemas
Operations