API and developers
Paging through API results
Most list endpoints page with limit and offset. The changes feed, KYB checks and prospects use a cursor. The Free plan returns only the first 10 search results.
limit and offset
Most endpoints that return lists take:
limit: how many results to return;offset: how many to skip.
The response includes total, limit and offset, so you can work out how many pages there are.
GET /company/search?q=builders&limit=50&offset=50| Endpoint | Default limit | Largest limit |
|---|---|---|
/company/search | 20 | 100 |
/company/recent | 25 | 100 |
/officers/search | 20 | 100 |
/filings/company/{number} | 25 | 100 |
/watchlist | 50 | 100 |
/lists/{id}/items | 100 | 1,000 |
Cursors
These endpoints use a cursor instead of an offset:
/changes/kyb/checks/prospects
Each response includes next_cursor. Send it back as cursor to get the next page. When there is no next_cursor, you have everything. Do not build or change cursors yourself; a changed cursor returns a 400 error.
For /changes, call GET /changes/cursor once to get a starting point, then keep the latest next_cursor so you only receive new changes.
On the Free plan
Free returns the top 10 search results and no further pages: limit is capped at 10 and offset is ignored. Autocomplete returns up to 5 names and the newest incorporations feed up to 5 companies. Full paging comes with Starter and above.
Tips
- Every page is a request and counts against your limits.
- Use the largest
limityou need, rather than many small pages.
Last updated 2 October 2026
Related articles
- API keys and authentication
- API rate limits and error codes (401, 403, 404, 429)
- Webhooks: get changes sent to your system
- Connect SI agents with the hosted MCP server
Still need help? Contact us, or if you have an account, open a support request.