---
title: "Delete an environment"
method: DELETE
path: "/projects/{project_id}/environments/{environment_id}"
tags: ["Environments"]
---

# Delete an environment

`DELETE /projects/{project_id}/environments/{environment_id}`

## Request

- Base URL: `https://app.honeybadger.io/v3`
- URL: `https://app.honeybadger.io/v3/projects/{project_id}/environments/{environment_id}`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/honeybadger/apis/honeybadger-api/docs/projects/:project_id/environments/:environment_id/delete.ts> (a function with typed inputs; its response is checked against the schema)

Deletes an environment. Its faults and notices stay, and its name is removed from integrations' `excluded_environments`. The next notice or deploy under that name creates it again, with `notifications: true`.

## Path parameters

- `project_id` string, required
- `environment_id` string, required

## Response `204`

Environment deleted

## Other responses

- `401`: The credential is missing, invalid, expired or revoked (`unauthorized`), or was sent in a way v3 doesn't accept (see the examples).
- `403`: The credential isn't allowed to do this. `error.code` says why. An account or project the credential doesn't cover is 404 `not_found`, not 403.
- `404`: Resource not found
- `422`: No path names the account, so the API token has to. This is returned when the token covers more than one account and the account a request applies to cannot be determined. Use a token bound to a single account.

---

[API](https://skmtc.dev/honeybadger/apis/honeybadger-api.md) - [All operations](https://skmtc.dev/honeybadger/apis/honeybadger-api/llms.txt) - [OpenAPI document](https://skmtc.dev/honeybadger/apis/honeybadger-api/revisions/cbcff53f2c8a?raw)