Core Conceptsv1
Rate limits
Understand quotas, throttling responses, and safe retry behaviour.
Updated 12/07/2026
On this page
Limits
Rate limits protect platform stability and are evaluated by application, credential, workspace, product, and environment where applicable.
Throttled requests
A throttled request returns HTTP 429. Respect the retry guidance in the response, apply exponential backoff with jitter, and avoid synchronized retries.
Good practices
Cache safe responses where appropriate.
Avoid polling when webhooks are available.
Distribute background workloads rather than sending bursts.
Monitor quota and rate-limit usage in the developer console.
Contact support before planned high-volume events.