tessera

Removes any share, whoever uploaded it.

DELETE
/api/v1/admin/shares/{id}

Why this exists

The ordinary delete route asks whether the caller owns the share. An upload from a since-deleted account has no owner, so nothing could remove it. It kept serving, kept its place in the storage quota, and was never swept if it had no expiry and no use limit. This is the only way to reach one.

Errors

401 when nothing was signed in, 403 when the caller may not delete every share or used a bearer token, 404 when no share has that identifier.

session
cookietessera_session<token>

Set by POST /auth/login. A browser sends it automatically; it is HttpOnly, so page scripts cannot read or set it.

id*string

Which share

Response Body

It is gone

curl -X DELETE 'https://example.com/api/v1/admin/shares/string'
Empty