Skip to main content

Pagination Guide

Many endpoints support cursor-based pagination to efficiently navigate through large result sets. Here’s how to use it:

Basic Usage

Most list endpoints support two query parameters:
  • limit - Number of results per page (1-25, default varies by endpoint)
  • cursor - Opaque token for fetching the next page

Making Your First Request

The response includes a pagination object:

Getting the Next Page

Use the next_cursor from the previous response:

Complete Example

Important Notes

Changing filters mid-pagination: If you change query parameters (like platform, status, or query) between requests, the cursor will be invalidated. Start pagination from the first page when changing filters.
Cursor lifespan: Cursors are designed for immediate use within a pagination session. Don’t store them long-term as they may become invalid.

Pagination Tips

  1. Choose appropriate limits:
    • Use limit=25 (maximum) for bulk operations
    • Use smaller limits (5-10) for real-time updates
    • Default limits vary by endpoint
  2. Check for more pages: Always check has_more or whether next_cursor is null before making another request
  3. Rate limits: Even with cursors, you’re still subject to rate limits (100 req per minute)
  4. Platform filtering: When using platform parameter, only one platform value is supported per query (not comma-separated)