Rate limits Planned
Per-key rate limits are planned but not in place yet. Today the API does not
return X-RateLimit-* headers, and it does not answer 429 with a
Retry-After header.
If you expect sustained high volume, tell your Adzen account representative before you ramp up.
How to call the API in the meantime
- Call once per piece of content. On UGC, request each post once and
honor
no_ad_retry_after_secondsbefore asking about the same post again. See No match. - Retry server errors with backoff. Use exponential backoff with jitter for
5xxresponses. Don’t retry4xxresponses, which won’t succeed unchanged.
This page will describe the limits and headers once they are enforced.
Last updated on