Rate Limiting

The default API limit is 300 requests per minute. Authentication, public submission, AI, mapping, and other sensitive routes can use tighter route-specific limits. The operation’s runtime response is authoritative.

Rate limits can be keyed by credential, user, organization, or network context depending on the route. Do not assume that adding more API keys increases an organization’s supported throughput.

Response Headers

Rate-limited responses use HTTP 429. Inspect Retry-After and any X-RateLimit-* headers returned by the operation before retrying.

Client Strategy

1. Keep request concurrency bounded.
2. Cache stable reference data.
3. Request only the page and fields you need.
4. On 429, honor Retry-After and use exponential backoff with jitter.
5. Stop after a bounded number of attempts and surface the failure.

Avoid synchronized jobs that all start on the minute. Spread batch reads over time and checkpoint progress so a later run can resume without replaying every page.