Permanently delete a publication from the App Store. This removes the publication configuration and its URL — users who visit the publication URL after deletion will no longer be able to access or download the app.
This operation is permanent and irreversible. The publication's URL (distributionUrl) will stop working immediately. If you want to temporarily block access without deleting the publication, consider setting visibility to "inactive" via PUT – Update Published Application instead.
Deleting a publication does not delete the builds associated with it. The underlying builds remain in Applivery and can still be referenced by other publications.
Applivery provides two separate APIs for deleting publications, each requiring a different authentication credential.
Choosing the right API
| Integrations API | Workspace API | |
|---|---|---|
| Designed for | Per-app integrations and CI/CD pipelines | Workspace-level automation across multiple apps |
| Authentication | App API Token (per-app) | Service Account token (workspace-level) |
| App context | Implicit — token is already scoped to an app | Explicit — organizationId, storeId, and publishedApplicationId required in the path |
| Typical users | Scripts that clean up expired or superseded publications | Platform engineers managing publication lifecycle across multiple apps |
Integrations API
Use this endpoint when deleting publications within the scope of a single app. Authentication uses an App API Token, scoped to the specific app.
To create an App API Token, see Apps API Authentication.
Endpoint
DELETE https://api.applivery.io/v1/integrations/distributions/{publishedApplicationId}
Authentication
Authorization: Bearer <your_app_token>
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
publishedApplicationId |
String | Yes | The unique identifier of the publication to delete. E.g. 552ae3cfcb5abfc58d733b81. Returned by POST – Create a Published Application and GET – List of Published Applications. |
Example Request
curl 'https://api.applivery.io/v1/integrations/distributions/552ae3cfcb5abfc58d733b81' \
-X DELETE \
-H 'Authorization: Bearer YOUR_APP_TOKEN'
Responses
{
"status": true,
"data": {
"delete": "OK"
}
}
Each app must have at least one publication. If you attempt to delete the only remaining publication for an app, the request will be rejected with this error. Create a replacement publication before deleting the last one, or set its visibility to "inactive" instead.
{
"status": false,
"error": {
"code": 5044,
"message": "Can Not Delete Last PubApplication"
}
}
{
"status": false,
"error": {
"code": 4002,
"message": "No auth token"
}
}
{
"status": false,
"error": {
"code": 3001,
"message": "Entity not found"
}
}
Workspace API
Use this endpoint when deleting publications at the workspace level — for example, in automation pipelines that manage publication lifecycle across multiple apps using a single credential.
Authentication uses a Service Account token, which is workspace-scoped and not tied to any individual app.
To create a Service Account, see Service Accounts.
Endpoint
DELETE https://api.applivery.io/v1/organizations/{organizationId}/stores/{storeId}/pubApps/{publishedApplicationId}
Path parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
organizationId |
String | Yes | The unique identifier of your Applivery organization. |
storeId |
String | Yes | The unique identifier of the store (app project) the publication belongs to. |
publishedApplicationId |
String | Yes | The unique identifier of the publication to delete. |
Authentication
Authorization: Bearer <your_service_account_token>
Example Request
curl 'https://api.applivery.io/v1/organizations/ORG_ID/stores/STORE_ID/pubApps/552ae3cfcb5abfc58d733b81' \
-X DELETE \
-H 'Authorization: Bearer YOUR_SERVICE_ACCOUNT_TOKEN'
A successful deletion returns { "status": true, "data": { "delete": "OK" } }. The same 5044 constraint applies — the last publication of an app cannot be deleted via the Workspace API either.