environment_not_found

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "The requested environment does not exist.",
    "status": 404,
    "title": "Not Found",
    "type": "/errors/unkey/data/environment_not_found"
  }
}

​

Likely causes

• The environment slug is wrong.
• The project or app slug is wrong. That’s also reported as a missing environment. On deployments.createDeployment the message says so: The requested project, app, or environment does not exist.
• Your root key can’t read the environment. environments.getEnvironment, domains.createDomain, and deployments.createDeployment return this 404 instead of a 403. A key that can read the environment but lacks the action gets a 403 err:unkey:authorization:insufficient_permissions that names the missing permission.

​

How to fix

1. List the app’s environments with environments.listEnvironments and use the returned slug.
2. Check all three parts: project, app, and environment.
3. Check that the root key has the permission the endpoint needs on the environment.

​

Related errors

• err:unkey:data:app_not_found: the app doesn’t exist.
• err:unkey:application:invalid_environment_settings: the environment exists but its settings block deployments.
• err:unkey:data:policy_not_found: a gateway policy within the environment doesn’t exist.