rate_limited

{
  "meta": {
    "requestId": "req_3k2j1h0g9f8e7d6c"
  },
  "error": {
    "code": "err:frontline:client:rate_limited",
    "message": "Rate limit exceeded. Please try again later."
  }
}

​

If you’re calling an API hosted on Unkey

• Retry-After: seconds to wait before you retry, never lower than 1.
• X-RateLimit-Limit: how many requests the window allows.
• X-RateLimit-Remaining: how many you have left.
• X-RateLimit-Reset: when the window resets, as a Unix timestamp in seconds.

​

If you own this API

• The limit is too low for your real traffic.
• The identifier is too broad, so unrelated callers share one counter.
• The policy counts by a header that callers don’t send. When none of a policy’s identifiers are on a request, the request is rejected, so every request without that header gets this 429.

​

How to fix

1. Raise limit or shorten windowMs on the policy, or count by a more specific identifier.
2. For per-key limits, change the limit on the key or identity, or the ratelimits entry in the policy (name, and optionally limit, duration, and cost).
3. Make sure the identifier you count by is on every request the policy matches.
4. Create a new deployment. Policy changes only apply to deployments created after the change.

​

Related errors

• err:frontline:client:usage_exceeded: the key ran out of credits rather than requests per window.
• err:frontline:client:invalid_key: the key failed verification before limits were checked.