> ## Documentation Index
> Fetch the complete documentation index at: https://www.unkey.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Unkey is two separate products. Compute builds, deploys, and runs apps behind a gateway. API Management issues API keys, enforces rate limits, manages identities and permissions, and reports usage. Say which product a page belongs to; a reader can use either without the other.
> Every Unkey API endpoint is an HTTP POST to https://api.unkey.com/v2/{service}.{procedure} with a root key in the Authorization: Bearer header. Root keys are workspace scoped.
> Error codes have the form err:{system}:{category}:{specific} and each has a page at /errors/{system}/{category}/{specific}.
> The word environment means production or preview in Compute. Rate limiting has four meanings on this site; the glossary lists them.

# ratelimit_not_configured

> A gateway policy references a named rate limit that is not configured for the key or its identity.

<Danger>`err:frontline:config:ratelimit_not_configured`</Danger>

This error means the gateway can't enforce a named rate limit. The policy
references a limit that doesn't exist on the API key or its identity, and the
policy doesn't provide both an inline `limit` and `duration`.

The gateway rejects the request with `422 Unprocessable Entity`. This is a
configuration error, not an exhausted rate limit or an invalid API key.

The response message is:

> A rate limit required by the gateway policy is not configured for this key or its identity.

## If you're calling an API hosted on Unkey

Contact the API owner with the request ID. Retrying the same request won't fix
the missing rate-limit configuration.

## How to fix

If you own this API, check the rate-limit names in the matching key-auth policy.
For each required name, configure a matching rate limit on the key or its
identity, or supply both `limit` and `duration` in the policy to define an inline
limit.

This error code applies to gateway requests. The `verifyKey` API returns
`412 Precondition Failed` for a missing named rate limit.

## Related errors

* [`rate_limited`](/docs/errors/frontline/client/rate_limited): a configured rate limit is exhausted, so the gateway returns 429.
* [`invalid_configuration`](/docs/errors/frontline/config/invalid_configuration): the gateway policy can't be parsed or has an invalid value.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.