Endpoint
Query Parameters
integer
default:"15"
Number of records to return per page (max: 100)
string
Cursor for fetching next page of results
string
Cursor for fetching previous page of results
string
Filter customers by email address
string
Filter customers created after this timestamp (ISO 8601)
string
Filter customers created before this timestamp (ISO 8601)
string
default:"created_at:desc"
Sort order for results (created_at:asc|created_at:desc)
Response Format
Customer[]
Array of customer objects. See Customer Object for structure.
object
Examples
Basic List Request
Response
Filtered List Request
Pagination
The API uses cursor-based pagination to handle large collections of customers. To fetch the next page of results:-
Get the
aftercursor from the pagination object -
Pass it as the
afterparameter in your next request -
Repeat until no more
aftercursor is returned
For optimal performance, we recommend:
- Use reasonable page sizes (15-50 records)
- Cache results when possible
- Implement progressive loading in your UI
Error Responses
error
Invalid query parameters or malformed request
error
Missing or invalid API key
error
Insufficient permissions to list customers
Rate Limits
List operations are subject to the following rate limits:- 100 requests per minute per API key
- 1000 requests per hour per API key
Best Practices
- Efficient Filtering: Use filters to reduce response size and improve performance
- Cursor Management: Store cursors temporarily for pagination
- Bulk Operations: Use higher limit values for bulk data retrieval
- Error Handling: Implement proper retry logic for rate limits
- Data Freshness: Consider implementing cache invalidation strategies