Removes a backend.
Only forgets the backend: its row goes and the pool is rebuilt without it.
Nothing is deleted from the bucket or directory behind it, and a backend
that still holds a file refuses with 409, so removal never strands one.
The caller proves it is the account's owner first, by password or by a
two-step code (see [ConfirmOwnerRequest]): a session left open on a desk
should not be enough to unplug the place files are kept.
Errors
401 when nothing was signed in or the password or code is wrong, 403
when the caller may not write settings or used an API token, 404 when no
backend has that name, 409 when it still holds content, 429 when too
many codes have been wrong.
sessiontessera_session<token>Set by POST /auth/login. A browser sends it automatically; it is HttpOnly, so page scripts cannot read or set it.
name*stringWhich backend
application/json- body
Body of DELETE /account/mfa/totp and POST /account/mfa/recovery-codes.
Either proves it is the owner asking: the password, or a code.
code?|A code from the app, or a recovery code, instead of the password.
current_password?|The current password. Omitted by an account without one, which confirms
by a recent sign-in instead, or when code is given.
8 <= length <= 1024Removed
response?unknownapplication/jsonnullcurl -X DELETE 'https://example.com/api/v1/admin/storage/backends/string' \ -H 'Content-Type: application/json' \ -d '{}'null