err:frontline:client:insufficient_permissions403 Forbidden.
This isn’t err:unkey:authorization:insufficient_permissions, which is about a root key calling api.unkey.com.
Example response
If you’re calling an API hosted on Unkey
Changing the request won’t help. Ask the API owner to grant your key the permission or role this route needs, and give them the request ID.If you own this API
The key’s permissions, whether granted directly or through its roles, don’t satisfy your key-auth policy’spermissionQuery. A key passes the gateway exactly when it would pass keys.verifyKey with the same query. A rejected request doesn’t spend credits. Common causes:
- The key is missing the permission or role.
- The
permissionQueryis stricter than you meant.
How to fix
- Grant the missing permission or role to the key, or to its identity’s roles, in API Management. This applies on the next request.
- Or loosen the policy’s
permissionQuery, then create a new deployment. Policy changes only apply to new deployments.
invalid_configuration instead.
Related errors
err:frontline:client:invalid_key: the key didn’t verify at all.err:frontline:config:invalid_configuration: the permission query couldn’t be parsed.err:unkey:authorization:insufficient_permissions: a root key lacking permission on the Unkey API.