Ends every share one account uploaded.
Why this is not part of deleting the account
Removing an account and destroying what it uploaded are different acts. An operator clearing space wants this and not that; one removing a person who has left wants the reverse. Welding them together makes one impossible and the other a surprise.
It works on an account in any state, including one still in use. Reclaiming space from an active account should not require suspending it first.
Errors
401 when nothing was signed in, 403 when the caller may not delete every
share or used a bearer token, 404 when no account has that identifier.
sessiontessera_session<token>Set by POST /auth/login. A browser sends it automatically; it is HttpOnly, so page scripts cannot read or set it.
id*stringWhose shares to end
How many were ended
application/json- response
How many shares an operation ended.
removed*integerHow many were still live and are now finished.
The bytes go as the reaper reaches them, so this is not how much space has come back.
int640 <= valuecurl -X DELETE 'https://example.com/api/v1/admin/users/string/shares'{ "removed": 0}