Skip to main content
err:frontline:config:invalid_configuration
The API you called runs on Unkey, and the gateway can’t use the policies its owner deployed. The problem is in the owner’s configuration, not in your request. You get 422 Unprocessable Entity.
Example response
Browsers get the same error as an HTML page.

If you’re calling an API hosted on Unkey

Nothing you change will fix this. Requests keep failing until the owner fixes their configuration. Contact the API owner with the request ID.

If you own this API

Common causes:
  • A key-auth policy has a negative credits value.
  • A key-auth policy’s permissionQuery doesn’t parse.
  • An OpenAPI policy’s spec is invalid.
  • The policy configuration can’t be read at all.
For the first three, only routes that the broken policy matches fail. For the last one, every request to the deployment fails.

How to fix

  1. Open the gateway policies for the .
  2. Fix the broken value: make credits zero or positive, fix the permission query syntax, or repair the OpenAPI document.
  3. Create a new deployment. The running deployment keeps the broken configuration until you deploy again.
Last modified on October 6, 2026