api_not_found

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

​

Likely causes

• The ID has a typo, or isn’t an API ID. API IDs start with api_.
• The API was deleted.
• The API is in another workspace.
• Your root key can’t read the API. apis.getApi, apis.listKeys, and keys.createKey return this 404 instead of a 403, so a 404 doesn’t prove the API is gone. A key that can read the API but lacks the action gets a 403 err:unkey:authorization:insufficient_permissions that names the missing permission.

​

How to fix

1. Copy the ID from the dashboard or from the apis.createApi response.
2. If the ID is right, check that the root key has the permission the endpoint needs on that API.
3. If the API was deleted, create a new one. Deleting an API from the dashboard also deletes its keyspace and all its keys. Deleting it with apis.deleteApi removes only the API, and its keys can’t be reached through that apiId any more.

​

Related errors

• err:unkey:data:key_not_found: a key within the API doesn’t exist.
• err:unkey:application:precondition_failed: the API exists but isn’t set up for keys or for key recovery.
• err:unkey:application:protected_resource: the API can’t be deleted while delete protection is on.