রেট লিমিট
বাকেট, প্রতিটি রেসপন্সের হেডার, লিমিটার বিভ্রাটে কী হয় এবং সীমার নিচে থাকার উপায়।
Version v1 · updated 2026-02-01
Limits are per credential and per named bucket, not one global number. Data-plane reads are generous; anything that can be brute-forced or that causes outbound work is deliberately tight.
| Bucket | Applies to | Limit | Window |
|---|---|---|---|
| api.v1 | All REST data-plane calls | 600 | 60s |
| oauth.token | Token exchange and refresh | 60 | 60s |
| oauth.authorize | Consent screen starts | 20 | 300s |
| exports | Starting an export job | 10 | 600s |
| webhook.dispatch | Outbound deliveries to you | 600 | 60s |
| docs.tryit | The sandbox panel on this site | 20 | 300s |
Headers#
HTTP/1.1 200 OK
x-ratelimit-limit: 600
x-ratelimit-remaining: 587
x-ratelimit-reset: 2026-02-01T09:01:00Z
x-request-id: req_01JB4…On 429 the same headers are present plus `retry-after` in seconds. Sleep for exactly that long, with jitter, and do not open more connections to compensate.
When the limiter itself is down#
The limiter fails open — a limiter outage must not take the API down with it — but every fail-open is counted and alerted. Do not treat a missing `x-ratelimit-remaining` as permission to burst.