Documentation

Rate limits & quotas

Per-key request budgets, burst allowances, and back-off headers.

APIs protect upstreams with Kong rate-limiting plugins. Limits are set per API (and sometimes per route or method) by the producer.

Reading the headers

When rate limiting is enabled, responses include headers describing your remaining budget and when it resets. Use them to pace requests rather than hammering until you get a 429.

Handling 429 Too Many Requests

On 429, honour the Retry-After header and back off. Implement exponential back-off with jitter for resilience.

Requesting a higher quota

Need more headroom? Contact the API's owning team (listed on its catalog page) to discuss a higher tier.