precondition_failed

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "The requested API is not set up to handle keys.",
    "status": 412,
    "title": "Precondition Failed",
    "type": "/errors/unkey/application/precondition_failed"
  }
}

​

Likely causes

• The API isn’t set up for keys (The requested API is not set up to handle keys.).
• You asked for key recovery (recoverable: true or decrypt: true) on an API that doesn’t store recoverable keys.
• A rate limit you named in keys.verifyKey isn’t set on the key or its identity.

• The workspace has no active Compute plan, or compute is paused because the workspace reached its spend limit.
• You asked for a git deployment, but the app has no connected GitHub repository, or the Unkey GitHub App isn’t installed or can’t access the repository.
• You redeployed a deployment that never produced an image.
• The domain you’re verifying is already verified.

​

How to fix

• Use an API with key support, or check the API ID.
• Turn on recoverable keys for the API before you ask for recoverable: true or decrypt: true.
• Set the named rate limit on the key or identity before you check it.
• Connect the repository, or install the GitHub App from the link in the message.
• Choose a Compute plan under Plans, or raise or remove the spend budget under Settings > Billing.
• For an already verified domain, there’s nothing to do.

​

Related errors

• err:unkey:application:deployment_not_ready: a deployment lifecycle precondition on promote or rollback.
• err:unkey:application:invalid_environment_settings: the environment’s settings block the deployment.
• err:unkey:data:analytics_not_configured: analytics isn’t set up for the workspace.
• err:unkey:application:protected_resource: a delete was blocked by delete protection.