DocumentationOpen PingAgain
Browse

Developer API

Pagination, rate limits, and errors

Handle opaque cursors, request limits, retries, and structured errors.

Collection endpoints use cursor pagination. Request limits protect the shared Public Beta service.

Pagination

limit accepts values from 1 to 100 and defaults to 50. When a response includes a next cursor, pass it back exactly as returned. Do not decode it, construct offsets, or reuse a cursor with different filters.

Rate limits

The current limits are 600 requests per token per hour and 1,200 per source per hour. A 429 Too Many Requests response includes Retry-After.

Wait for that interval and add jitter before retrying. Replaying immediately can extend the failure and create unnecessary traffic.

Errors

Check the HTTP status and structured error code before deciding whether to retry. Correct validation and permission errors; retry only temporary server or provider failures. Treat 401 as a missing or invalid key, 403 as insufficient scope or policy, and 404 as unavailable to the authenticated account.

Do not log request credentials or private payloads while troubleshooting.

Next: see API authentication or use the API examples.