key_space_not_found

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "Keyspace \"ks_123\" does not exist.",
    "status": 404,
    "title": "Not Found",
    "type": "/errors/unkey/data/key_space_not_found"
  }
}

​

Likely causes

• You passed the API ID (api_...) instead of the keyspace ID (ks_...). They’re different values on the same API.
• The API behind the keyspace was deleted. Deleting an API from the dashboard also deletes its keyspace, so a policy that used to work can start failing.
• The keyspace is in another workspace.

​

How to fix

1. Use the keyspace ID shown on the API in the dashboard, or returned by apis.getApi.
2. Fix every keyspace ID in the policy. gateway.setPolicies and gateway.updatePolicy stop at the first missing one, so several bad IDs show up one at a time.

​

Related errors

• err:unkey:data:key_auth_not_found: the deprecated deploy endpoint couldn’t find a keyspace.
• err:unkey:data:policy_not_found: the policy id doesn’t exist.
• err:unkey:data:api_not_found: the API itself doesn’t exist.