Removes several shares at once, whoever uploaded them.
DELETE
Each one as DELETE /admin/shares/{id} would, logged the same way. A
failure does not stop the rest.
Errors
400 for more than 200 identifiers, 401 when nothing was signed in, 403
when the caller may not delete every share or used a bearer token, 404
when this instance has no administration. Problems with individual shares
are in the body.
sessioncookie
tessera_session<token>Set by POST /auth/login. A browser sends it automatically; it is HttpOnly, so page scripts cannot read or set it.
application/json- body
Body of DELETE /admin/shares.
ids*array<string>Share identifiers, at most 200.
What happened to each share
application/json- response
What an administrative batch delete did, share by share.
deleted*array<string>The identifiers that were deleted, as they were sent.
failed*array<>The identifiers that were not, and why.
curl -X DELETE 'https://example.com/api/v1/admin/shares' \ -H 'Content-Type: application/json' \ -d '{ "ids": [ "string" ]}'{ "deleted": [ "string" ], "failed": [ { "error": "not_found", "id": "string" } ]}