Skip to main content

​
Rate Limits and Query Budgeting

​
Principles

  • Prefer batched reads over endpoint fan-out.
  • Cache stable reads on your side where possible.
  • Use backoff on 429 responses.
  • Separate critical writes from opportunistic reads.

​
Client controls

  • request concurrency caps
  • retry budget caps
  • per-workspace request budget controls
  • circuit breaker for persistent upstream errors
Budget your analytics and detail-page reads separately. Keep default dashboards fast and cached, and reserve higher-cost drilldowns for explicit operator actions.

​
Analytics budget guidance

Avoid running high-frequency polling across multiple tabs simultaneously. Prefer snapshot-style reads and explicit refresh actions for detail pages.
  • /developer/error-model-and-retries
  • /help/analytics/read-workspace-campaign-and-link-analytics