Deletes several of the caller's shares in one request.
Each one as DELETE /shares/{code} would: its objects first, each from the
backend holding it, then its row. A failure does not stop the rest.
Repeated codes are deleted once.
Signed in only: a management token belongs to one share, so there is nothing for a batch to check it against.
Errors
400 for more than 200 codes, 401 when nothing was signed in, 403
when the credential does not carry shares:delete. Problems with
individual shares are in the body, not the status.
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 /shares.
codes*array<string>Retrieval codes of the caller's own shares, at most 200.
What happened to each share
application/json- response
What a batch delete did, share by share.
Never all-or-nothing. A client keeps the failed ones selected for a retry;
only the codes listed in deleted are gone.
deleted*array<string>The codes that were deleted, as they were sent.
failed*array<>The codes that were not, and why.
curl -X DELETE 'https://example.com/api/v1/shares' \ -H 'Content-Type: application/json' \ -d '{ "codes": [ "string" ]}'{ "deleted": [ "string" ], "failed": [ { "code": "string", "error": "not_found" } ]}