Delete history backupAdded in 8.10

DELETE 
/backups/history/:backupId

Strongly Consistent About endpoint data consistency

Deletes the history backup with the given id, by deleting every snapshot that makes it up.

Only available on clusters whose secondary storage is Elasticsearch or OpenSearch.

Required permissions

When authorization is enabled, this endpoint requires the following permission. See resources and permissions to learn more.

Resource type	Permission
BACKUP	DELETE

Request

Responses

204

The backup has been successfully deleted.

401

The request lacks valid authentication credentials.

Response Headers

WWW-Authenticate

403

The request is forbidden, either because the authenticated caller lacks the required BACKUP permission, or because the cluster's secondary storage is neither Elasticsearch nor OpenSearch and therefore cannot serve history backups. The problem detail says which of the two applies.

404

A backup with the given id does not exist.

500

An internal error occurred while processing the request.

503

The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains RESOURCE_EXHAUSTED. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .