Skip to main content
Each API key has its own request budget, enforced as a short rolling window. When you exceed it, the API responds with:
with HTTP status 429.

​
Handling 429

  • Treat 429 as temporary, not a block. Retry with exponential backoff (for example 1s, 2s, 4s).
  • Spread load across time rather than bursting — a steady rate stays under the limit better than spikes.
  • If you consistently hit the limit, your plan’s budget may be too low for your volume. Dedicated concurrency plans are available for steady, high-volume pipelines — talk to us.
Limits are per key, so splitting unrelated workloads across separate keys keeps one noisy job from rate-limiting another.