delete object. Missing objects will not return a NotFound error.
Query parameters
delete entry without tombstone when possible EXPERIMENTAL
Response
object deleted successfully
Changes
Changed in 4 of the 52 revisions of this API.17
- ○
added the non-success response with the status
400response-non-success-status-added
- ○
- ○
added the new optional
queryrequest parameterno_tombstonenew-optional-request-parameter
- ○
- ○
added the non-success response with the status
429response-non-success-status-added
- ○
removed the non-success response with the status
420response-non-success-status-removed
- ○
- ●
deleted the
queryrequest parameterno_tombstonerequest-parameter-removed
- ○
added the non-success response with the status
420response-non-success-status-added
- ○
removed the non-success response with the status
400response-non-success-status-removed
- ○
removed the non-success response with the status
429response-non-success-status-removed
This revision also has 14 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ●