List Customers
Intent
Reads the available customers as a pageable collection without changing them.
When to call it
Call this when an interface, sync, or support workflow needs to inspect customers. Use the filters and paging controls shown below to limit the result.
Access boundary
Authorize the request with a token that carries customers:read or customers:write.
Successful result
A successful request returns 200. The response schema below defines the body your integration receives.
Operational notes
List customers.
Scopes: customers:read customers:write
Authorizations
You can generate an Organization Access Token from your organization's settings.
Query Parameters
Filter by organization ID. The organization ID.
"1dbfc517-0bbf-4301-9ba8-555ca42b9737"
Filter by exact email.
Filter by name, email, or external ID.
Filter by active customers, i.e. customers with at least one trialing, active or past_due subscription.
Page number, defaults to 1.
Size of a page, defaults to 10. Maximum is 100.
Sorting criterion. Several criteria can be used simultaneously and will be applied in order. Add a minus sign - before the criteria name to sort by descending order.
created_at, -created_at, email, -email, name, -name Filter by metadata key-value pairs. It uses the deepObject style, e.g. ?metadata[key]=value.