Skip to main content
Partner API list endpoints accept page (default 1) and usually a search string filter. Card and transaction lists also accept page_size (default 50).
For card and transaction lists, page_size accepts positive integers. Values above 100 are clamped to 100; zero, negative, and non-numeric values return 400 Bad Request. Responses are page wrappers (for example CardPageResponse, TransactionPageResponse) containing the current page of results and paging metadata from the serializer.

​
Pattern

  1. Start at page=1
  2. If more results exist, request page=2, page=3, …
  3. Use the response count, current_page, and effective page_size to determine when all results have been read
Exact paging fields follow the OpenAPI response schemas in the API Reference.