Permanently removes a specific version of an enterprise application from Esper. If the target version is currently referenced by one or more blueprints, the version must be removed tfrom the blueprint before the version can be deleted. If no blueprint references exist, the version is deleted outright and the endpoint returns HTTP 204.

About Delete App Version

Each application in Esper can have multiple uploaded versions, and individual versions can be removed without deleting the parent application. The blueprint authors must explicitly confirm intent to orphan those references.

Key Fields / Query Parameters

version_id — UUID of the specific app version to delete; required path parameter

application_id — UUID of the parent application; required path parameter

enterprise_id — UUID of the enterprise; required path parameter

request_id — Query parameter; if a prior call returned a request_id (because the version is in use by blueprints), pass it here to confirm deletion and clear the cache entry

Common Use Cases

Removing a recalled or defective APK version that should no longer be deployable. Cleaning up old test builds or pre-release versions after a stable version is promoted. Freeing storage and reducing version clutter in the application library.

Best Practices

Always check the response code on the first call — a 200 with a request_id body means the version is blueprint-referenced and requires a second confirmation call; a 204 means it was deleted immediately. Audit which blueprints reference the version before deleting to avoid breaking active device configurations. Coordinate with teams managing blueprints before removing versions that may be in production use.

Workflow

Call DELETE /api/v1/enterprise/{enterprise_id}/application/{application_id}/version/{version_id}/ with path parameters only. If response is 204, deletion is complete — no further action needed. If response is 200 with a request_id, resubmit the same request appending ?request_id={returned_id} to confirm the deletion.