List all customers
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.
Authorizations
Use your OAuth client credentials to obtain a short-lived Bearer token from POST /oauth/token.
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.
PENDING, PROCESSING, VERIFIED, REJECTED Filter by customer type. Upper-case input is normalized to lower-case.
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.
x >= 1Response
Customers retrieved successfully. The response body is the legacy CustomerListResponse shape by default, and the PaginatedCustomerListResponse shape when paginate=true was sent.

