Retrieve customers for your business. Supports optional exact-match filters on email, id_number, registration_number, verification_status, and type, and opt-in pagination via paginate=true. Filters and pagination compose.
When paginate is omitted or not truthy, the response shape is unchanged ({message, data: [...]}). When paginate=true, the response is a paginated envelope ({message, data: [...], links: {...}, meta: {...}}) with 15 items per page. Use the ?page=N query string (in addition to paginate=true) to fetch subsequent pages.
Ordering: the paginated path returns results newest-first (by created_at descending). The default unpaginated path preserves the legacy database-order semantics for backwards compatibility — if you need a guaranteed order, opt in to paginate=true.
Required scope: customer:read.
Authorization
oauth2ClientCredentials customer:readUse your OAuth client credentials to obtain a short-lived Bearer token from POST /oauth/token.
In: header
Scope: customer:read
Query Parameters
Exact-match filter on customer email. Validated as a plain string (not the email rule) so any value you successfully created the customer with is recoverable.
Exact-match filter on the customer's government-issued ID number.
Exact-match filter on the business customer's registration / incorporation number.
Filter by verification status. Lowercase input is normalized to upper-case.
Value in
- "PENDING"
- "PROCESSING"
- "VERIFIED"
- "REJECTED"
Filter by customer type. Upper-case input is normalized to lower-case.
Value in
- "individual"
- "business"
Opt in to the paginated response shape. Pass true (or any truthy value, e.g. 1) to receive {message, data, links, meta} with 15 items per page. Any other value — or omitting the parameter — returns the legacy {message, data} shape unchanged.
Page number to fetch when paginate=true. Defaults to 1. Ignored when pagination is not enabled.
1 <= valueResponse Body
application/json
application/json
application/json
curl --request GET \ --url 'https://example.com/api/external/customer?paginate=true'{ "message": "Customers retrieved successfully.", "data": [ { "id": "customer_123", "type": "individual", "first_name": "John", "last_name": "Doe", "business_name": null, "registration_number": null, "id_number": "A01234567", "email": "john@example.com", "phone": "+2348012345678", "verification_status": "VERIFIED", "created_at": "2026-01-15T10:30:00Z" }, { "id": "customer_456", "type": "business", "first_name": null, "last_name": null, "business_name": "Acme Corp", "registration_number": "RC1234567", "id_number": null, "email": "contact@acme.com", "phone": "+2348012345679", "verification_status": "VERIFIED", "created_at": "2026-01-14T09:20:00Z" } ]}POSTCreate a customer
Create a new customer. Verification stays `PENDING` until the type-specific verification flow completes. **For `type=individual`**, `id_type` and `id_number` are required. After creation, upload identity files via the legacy KYC flow (see [Creating your first payout](/docs/guides/creating-first-payout)). Only Driver's License, Passport, or Resident Permit are accepted as `id_type`. **For `type=business`**, `business_name` + `registration_number` + `incorporation_country` are required. The legacy `id_type` / `id_number` fields are no longer required (still accepted for back-compat — when supplied, `id_type` must be `certificate_of_incorporation`). After creation, follow the [Business customer KYB](/docs/guides/kyb/overview) flow: register beneficial owners, upload owner ID files, register KYB documents, then call `/submit`. ID cards (National Identity Cards) are not accepted at any stage. All uploaded documents must be clear, legible, and authentic — unclear images will be rejected. Fraudulent or falsified documents will result in the customer being permanently blacklisted from the platform. Required scope: `customer:write`.
GETGet a customer
Retrieve customer details by ID. Required scope: `customer:read`.