invalid_key

{
  "meta": {
    "requestId": "req_3k2j1h0g9f8e7d6c"
  },
  "error": {
    "code": "err:frontline:client:invalid_key",
    "message": "Authentication failed. The provided API key is invalid."
  }
}

​

If you’re calling an API hosted on Unkey

​

If you own this API

• The key doesn’t exist or was deleted.
• The key is disabled or expired.
• The key is from a keyspace your key-auth policy doesn’t list.
• The workspace that owns the key is disabled.

​

How to fix

1. Look the key up in the dashboard or with keys.getKey. Check that it’s enabled, not expired, and in a keyspace the policy accepts.
2. If callers hold keys from a keyspace you added recently, add that keyspace to the policy and create a new deployment. Policy changes only apply to deployments created after the change.
3. If the key looks fine, check whether the workspace that owns it is disabled.

​

Related errors

• err:frontline:client:missing_credentials: no key was found at all.
• err:frontline:client:insufficient_permissions: the key is valid but lacks permissions.
• err:unkey:data:key_not_found: the equivalent when you look a key up through the Unkey API rather than the gateway.