curl -X DELETE "https://api.scanova.io/media/bulk/12/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
Media Library
Delete a bulk media batch
DELETE /media/bulk//
DELETE
/
media
/
bulk
/
{pk}
/
curl -X DELETE "https://api.scanova.io/media/bulk/12/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
Deletes a bulk media batch owned by this account, on the Management API host (
A successful call returns
api.scanova.io), authenticated with your raw Management API key.
DELETE https://api.scanova.io/media/bulk/{pk}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
integer
required
The batch’s
id.curl -X DELETE "https://api.scanova.io/media/bulk/12/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
204 No Content. 404 if pk isn’t a batch owned by this account.
Deleting a batch doesn’t delete the individual files uploaded into it — use Delete a file or Bulk-delete files by path to remove those separately.
Related
- Retrieve a bulk media batch — check before deleting.
- List bulk media batches — see what else exists.
- Management API overview — the auth scheme and quota rules that apply to this endpoint.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: 401f7ac837da42b97f613d789819ff93537bee6a. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Path Parameters
Response
Batch deleted.
Was this page helpful?