Delete an application version

DELETE

/api/v1/applications/{id}/versions/{version}

const url = 'http://localhost:3000/api/v1/applications/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/versions/2.0.18';
const options = {method: 'DELETE', headers: {'X-API-Key': '<X-API-Key>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request DELETE \
  --url http://localhost:3000/api/v1/applications/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/versions/2.0.18 \
  --header 'X-API-Key: <X-API-Key>'

Soft-deletes one version that no registry provides (FM-1467). Refused with 409 while any deployment other than REMOVED references the version, or while a registry source still provides it. When the last version goes, the application goes too. A later sync that provides the version again restores it. Needs the applications:delete permission in the tenant; superadmin is not required.

Authorizations

api-key
bearer

Parameters

Path Parameters

required

string format: uuid

Application package UUID

version

required

string

Example

2.0.18

Version string

Header Parameters

x-organization-id

string format: uuid

UUID of the organization (tenant) the request acts in. It selects the tenant and grants nothing: the server checks membership or an open tenant switch. Not needed for global operations. A malformed value returns 400. API keys are fixed to their own organization; another organization returns 403. The x-organization-source header grants nothing.

Responses

204

Version deleted

400

Invalid application id or version

403

Forbidden — caller lacks required permission

404

Version not found

409

Active deployments still reference the version, or a registry still provides it