Skip to main content

Pagination

List endpoints that can return large result sets use cursor-based pagination.

How it works​

  1. Make the initial request.
  2. If more results exist, the response's meta object includes a next_cursor token.
  3. Request the next page by passing that token back as the cursor query parameter.
  4. Repeat until next_cursor is empty (or absent), which means you've reached the end.
# First page
curl "https://api.abcsalesbot.com/v1/<resource>" \
  -H "Authorization: Bearer $ABC_API_KEY"

# Next page: pass the previous response's meta.next_cursor
curl "https://api.abcsalesbot.com/v1/<resource>?cursor=eyJpZCI6MTIzfQ" \
  -H "Authorization: Bearer $ABC_API_KEY"

Treat the cursor as an opaque token: don't parse, construct, or persist it across schema changes. Check each endpoint in the API Reference for whether it paginates and any additional filters it accepts.