Skip to content
Esc
↑↓navigate↵open⌘Jpreview
On this page

Rate limits

Request limits for your organization and the headers that report them.

These limits apply to all requests to the Doss API. Doss enforces two request rate limits:

  • A limit for each API key
  • A limit for the organization, shared by all of its API keys

When a request exceeds either limit, the API returns an error.

Request Rate Limits

Scope Limit
Each API key 10 requests per second
Organization, across all API keys 25 requests per second

What Happens If You Exceed a Limit

The API returns 429 Too Many Requests with the error code rate_limited. The response includes a Retry-After header with the number of seconds to wait before retrying.

In rare cases, a 429 comes from a limit shared by the whole API rather than from your key or organization. These responses include Retry-After but no RateLimit fields, so always use Retry-After to decide when to retry.

Monitoring Your Usage

Every response has information regarding your usage:

  • RateLimit-Limit: requests allowed in the current window
  • RateLimit-Remaining: requests left in the current window
  • RateLimit-Reset: seconds until the window resets
  • Retry-After: sent with 429 responses, seconds to wait before retrying

Reducing Your Request Volume

  • Request up to 1,000 records per page with limit.
  • Use fields to return only the fields you need.
  • To sync changes, filter on updated_at with gt instead of re-reading whole tables.

Increasing Your Limits

If your use case needs higher limits, contact your Doss account team.