key_auth_not_found

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "The specified keyspace was not found.",
    "status": 404,
    "title": "Not Found",
    "type": "/errors/unkey/data/key_auth_not_found"
  }
}

​

Likely causes

• The keyspace ID has a typo, or isn’t a keyspace ID. Keyspace IDs start with ks_.
• The keyspace is in another workspace.

​

How to fix

1. Pass the keyspace ID of an API in the same workspace, or leave out keyspaceId.
2. For new integrations, use deployments.createDeployment and set key auth with gateway.setPolicies. A missing keyspace there returns err:unkey:data:key_space_not_found.

​

Related errors

• err:unkey:data:key_space_not_found: the same problem on the gateway policy endpoints.
• err:unkey:data:api_not_found: the API doesn’t exist.
• err:unkey:data:project_not_found: the project doesn’t exist.