Throttle Signal
When throttled, the API returns429 Too Many Requests with:
Retry-AfterX-RateLimit-LimitX-RateLimit-RemainingX-RateLimit-Reset
Retry Strategy
- Respect
Retry-Afterexactly. - Apply exponential backoff with jitter.
- Reuse the same
Idempotency-Keyfor retried writes. - Do not send parallel retries for the same business action.
Client Architecture Recommendations
- Use a client-side write queue or concurrency cap so retries stay controlled.
- Use token-bucket or leaky-bucket throttling in your client.
- Separate read and write retry policies.
- Trigger alerts when sustained
429exceeds your SLO threshold.