Skip to main content
Many API resources support fetches via list API methods. For example, you can list redemptions, publications, customers, products, and more. These list API methods often share query parameters such as limit, created_at, updated_at, and order. Availability and allowed values depend on the endpoint. Check the endpoint page for the full parameter list.

Paging the results

Some of the list API methods use the page query parameter to display another page of results. However, the following list API methods use the starting_after_id query parameter: The response to these methods may include a more_starting_after key that takes a string value with an ID. Use this ID with the starting_after_id query parameter to display another page of results.

Cursor pagination (Loyalty v2)

Loyalty v2 list endpoints use cursor pagination instead of page or starting_after_id. Typical response shape:
How to page results:
  1. Call the list endpoint without cursor to get the first page.
  2. If cursor.next is present, call the same endpoint again with ?cursor={cursor.next}.
  3. Stop when cursor is null or cursor.next is missing.
  4. Treat cursor.expires_at as the validity window for that cursor value. Request a new first page if the cursor expires.
Cursor prefixes differ by resource (for example lcrsctx_ for card transactions and lcrsmbr_ for members). Always pass the exact cursor.next value returned by the previous response. See the Loyalty v2 endpoint pages under API reference for resource-specific cursor patterns.

Response format

The listing method returns a dictionary with a data property that contains an array of resources. The maximum number of resources returned is determined by the limit query parameter. If no more resources are available, the resulting array on a given page will be empty. The result can be narrowed down according to the specified (or default) filters.

Shortcuts

List API methods offer query parameter shortcuts that map to internal filters. Each resource enables a specific set. If you need advanced options, read the next section. For publications, voucher_type matches with a starts-with condition, not an exact match.

Advanced filters for fetching resources

API methods for fetching resources also accept nested filters query parameters for more precise criteria. For voucher filters[active] and filters[redemption_status], send one condition key per request. Only the first condition key is applied.
Last modified on November 9, 2026