---
title: "Delete an application"
method: DELETE
path: "/v1/enterprise/{enterprise_id}/application/{application_id}/"
tags: ["esper_cloud_api_Application V1"]
---

# Delete an application

`DELETE /v1/enterprise/{enterprise_id}/application/{application_id}/`

Permanently deletes an Android application record and all of its associated versions from the enterprise.

This operation is irreversible; the application and every version uploaded under it are removed entirely. Returns HTTP 204 with no response body on success.

**About Delete Application**

This endpoint is part of the Application V1 family, which manages the enterprise's Android app library. Deleting an application removes the top-level app record and cascades to all associated ApplicationVersionV1 records — every version uploaded under this application_id is deleted along with it. The app will no longer appear in the Android app inventory and cannot be targeted for installation or policy assignment. You must remove the application from all assoicated blueprints (and bluperint versions) before calling this endpoint.

There are two other application API families with distinct scopes:

Tenant Apps (/v2/tenant-apps/...) — manages uploaded apps for iOS and Windows platforms. Deletions of iOS or Windows apps are handled there.
Device Apps (/v2/devices/{deviceId}/device-apps/ and GET /v2/device-apps) — queries app install state on devices for iOS and Windows app types. This family does not perform deletions from the app library.

If you only need to remove a specific version rather than the entire app, use the version-level delete endpoint instead. There is no soft-delete or recovery path for this operation.

**Key Fields**

enterprise_id (path, required) — UUID of the enterprise
application_id (path, required) — UUID of the Android application to delete

**Common Use Cases**

Removing an Android app that was uploaded in error or is no longer relevant to the fleet

Cleaning up the Android app library during a fleet restructure or platform migration

Purging outdated or retired apps that should not be available for future installation

**Best Practice**

Verify the correct application_id using GET /v1/enterprise/{enterprise_id}/application/{application_id}/ before issuing DELETE — there is no undo

Check whether any devices still have the app installed before deleting; use GET /v1/enterprise/{enterprise_id}/application/{application_id}/version/{version_id}/installdevices per version to audit coverage

To delete iOS or Windows apps, use the Tenant Apps family (DELETE /v2/tenant-apps/{appId}) instead — this endpoint only covers the Android app library

If you only want to remove a specific version, use the version-level delete endpoint rather than deleting the entire application record

**Workflow**

Confirm the target app with GET /v1/enterprise/{enterprise_id}/application/{application_id}/

Optionally audit installed devices per version using the installdevices endpoint

Call DELETE /v1/enterprise/{enterprise_id}/application/{application_id}/

Expect a 204 response with an empty body confirming deletion

## Path parameters

- `application_id` string, uuid, required
- `enterprise_id` string, required

## Response `204`

The resource was deleted successfully.

## Other responses

- `401` — Authorization information is missing or invalid.
- `403` — Forbidden, no permission to perform this action.
- `404` — Not Found.
- `500` — Internal server error

---

[API](https://skmtc.net/esper/apis/esper-api-reference.md) · [All operations](https://skmtc.net/esper/apis/esper-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/esper/esper-api-reference/revisions/e1f64cbb488e/schema)