Pagination Behavior

While several endpoints support pagination (indicated by a Paged appended in the endpoint name), it should be noted that it will still retrieve the entire result set on the backend before slicing it into pages.

This means pagination does not reduce the number of records evaluated, and will not help avoid hitting the API usage limit if your request matches too many results.

Relevant API Endpoints

getEventListPaged

getHistoryListPaged

getCondensedOwnerOperatorPaged

getBulkAircraftExportPaged

getContactListPaged

Example Scenario

  1. Account has a 100,000 record API export limit
  2. Their request matches 250,000 records
  3. They attempt to paginate with 2,000 records per page (Page 1, Page 2, etc.)
  4. The backend still pulls the full 250,000
  5. Call fails with message: ERROR: RESULTS EXCEEDED LIMITS – [ RESULTS: 250000 LIMIT: 100000 ]

Recommended Action

Please contact support to discuss your call export limit. We may be able to advise on alternative strategies, increase your limit, or provide structured data outside the API.

 

Was this article helpful?

/