Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

As of Versionproduct version 2021 Winter | component version 2021 Winter
Request MethodDELETE
Response FormatJSON
Description

Deletes multiple objects specified by ID in the JSON request body.

A delete permission is required for all objects. A folders can not be deleted, if it is not empty.
If the object for at least one ID can not be found or can not be deleted, the whole request fails.

The number of objects that can be deleted via this endpoint is limited to 100.

Other properties beside system:objectId in the request body are just ignored. Notably objects found by a search request can be deleted by using the result of a the search request unmodified as the request body for the delete request.

Request HeaderContent-Type: application/json
Request Example

The new metadata is passed in the request body in JSON format.

{
	"objects": [{
		"properties": {
			"system:objectId": {
				"value": "cdc7095f-a5ce-486d-92a7-6d0955d969ee"
			}
		}
	},
	{
		"properties": {
			"system:objectId": {
				"value": "cdc7106f-a5ce-597d-92a7-1d1166d171ee"
			}
		}
	}]
}

Result Example

no result

Response
Meaning of the response status codes:

200 OK

All DMS objects has been deleted

403 Forbidden

Insufficient permissions to perform a delete action.

404 Not Found

At least one specified object can not be found or permissions are insufficient.

409 Conflict

At least one specified object can not be deleted due to retention (for more details click here).

  • No labels