unkey/data/key_not_found

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "We could not find the requested key.",
    "status": 404,
    "title": "Not Found",
    "type": "/errors/unkey/data/key_not_found"
  }
}

​

Likely causes

• You sent the secret key string where a keyId is expected.
• The key was deleted.
• The key ID is from another workspace, such as a staging workspace used with a production root key.
• On keys.whoami, which takes the key string, the string doesn’t match any key.

​

How to fix

1. Use the keyId returned when the key was created. It starts with key_.
2. If you lost it, list keys with apis.listKeys to find it.
3. If the key was deleted, create a new one. Deleted keys can’t be restored through the API.

​

Related errors

• err:unkey:authentication:key_not_found: the root key in the Authorization header isn’t valid.
• err:unkey:data:api_not_found: the API that would own the key doesn’t exist.
• err:unkey:data:key_auth_not_found: the keyspace id doesn’t exist.