Skip to main content
Pagination lets you retrieve large result sets in pages instead of one large response. This keeps requests fast and reliable, and reduces memory and timeout risk. Use the pagination parameters for each endpoint to request the next page until there are no more results. Remember that each page is a separate request that counts toward your rate limits (and any applicable credits), so choose a reasonable page size.

​
How it works

Pagination uses two query parameters:
  • page — zero‑based page index (use 0 for the first page)
  • limit — number of items to return on that page
Defaults (if not specified):
  • page: 0
  • limit: 25
Pagination starts at page=0 because most programming contexts use zero-based indexing. This keeps the logic consistent with common programming conventions and makes the code easier to reason about on both our side and yours. Upper bound:
  • limit: 5000
We use upper-bound limiting to break a potentially huge result set into smaller, faster queries, which keeps response times low and prevents timeouts when working with large datasets.

​
Example

If you have access to a search with ID 5432 and you want the second 500 results, request page 1 with a limit of 500: 
https://app.tryspecter.com/api/v1/searches/5432/results?page=1&limit=500
⌘I