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.
Authorizations
Query Parameters
Return only records matching organization ID. Identifier of the organization.
"1dbfc517-0bbf-4301-9ba8-555ca42b9737"
Return only records matching exact email.
Return only records matching name, email, or external ID.
Return only records matching active customers, i.e. customers with at least one trialing, active or past_due subscription.
Results page to return. The first page is used by default.
Records returned per page. Defaults to 10 and accepts up to 100.
Sort rules applied from left to right. Prefix any rule with - to reverse it into descending order.
created_at, -created_at, email, -email, name, -name Return only records matching metadata key-value pairs. It uses the deepObject style, e.g. ?metadata[key]=value.