API Rate Limits

The DevTune API enforces per-key rate limits to ensure fair usage. Limits are based on your subscription plan tier.

Limits by Plan

Rate limits are applied per API key, not per account. If you have multiple keys, each has its own independent limit.

Every API response includes headers that tell you your current rate limit status:

Header	Description
`X-RateLimit-Limit`	Maximum requests allowed per window
`X-RateLimit-Remaining`	Requests remaining in the current window
`X-RateLimit-Reset`	Unix timestamp (seconds) when the window resets

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 87
X-RateLimit-Reset: 1707400800

If you exceed your rate limit, the API returns a 429 Too Many Requests response:

{
  "error": "rate_limit_exceeded",
  "message": "Rate limit exceeded. Please try again later.",
  "status": 429
}

The response includes rate limit headers so you know when to retry.

Check the headers before making rapid requests. Use X-RateLimit-Remaining to pace your calls.
Use exponential backoff when you receive a 429. Wait until the X-RateLimit-Reset timestamp before retrying.
Cache responses where possible. Most DevTune data updates once per day (after scheduled tracking runs), so caching for several minutes is usually appropriate.
Batch your reads rather than polling frequently. Pull data once and process it locally.