Resource Deletion

A SERVER MAY support resource deletion requests.

If implemented, a SERVER MUST treat resource deletion requests as transactions, i.e., requests MUST either fully succeed or fail entirely leaving no partial side-effects.

Resource deletion requests MUST be performed through HTTP DELETE requests (see Messages).

Resource deletion requests MUST be supported on individual resource routes (see routes.adoc#anchor-resource-routes) of the identified resource.

Resource deletion requests MUST NOT include a body, as described in message.adoc#anchor-request.

The example below demonstrates a valid resource deletion request to delete an event resource.

DELETE /2022-04/events/123 HTTP/1.1

A SERVER MUST respond to successful requests with a status code 204 No Content.

A SERVER MUST NOT include a body message in responses to successful deletion requests.

The following example demonstrates the response to a successful resource deletion request.

HTTP/1.1 204 No Content

A SERVER MUST reply to resource deletion requests with an error response in the following cases, using the adequate error codes (see message.adoc#anchor-error).

  • the resource identified by the route’s id does not exist

  • the CLIENT does not have authorization to delete the resource