Hey, human!
HTTP/2 200 OK content-type: text/markdown; charset=utf-8 vary: accept, user-agent x-agent: [ai_agent]
Loading the agent response…
Move a file or folder to the bin; if a transfer holds it, 409 transfer_active until confirm_delete_transfers=true
Moves a file or folder to the bin, where the app's retention rule applies and restoreFile can bring it back. If a transfer holds the item the answer is 409 transfer_active and its details name the transfers; repeat with confirm_delete_transfers=true to delete those transfers as well. Protected items are 403 protected. Returns deleted: true and the ids of any transfers deleted with it. Needs files:write.
Do this with AI
I want to move a file or folder to the bin; if a transfer holds it, 409 transfer_active until confirm_delete_transfers=true. Use the Tarkle API. Read the reference for this operation and follow it exactly: https://project-03b42162.restlessdocs.com/endpoint/deletefile.md Authenticate with your API key as a Bearer token in the Authorization header. Then make the request for me and tell me what came back.
Paste this into Claude, Cursor, or any AI assistant and it will do it for you.
https://tarkle.com/api/v1/files/{id}curl --request DELETE \
--url https://tarkle.com/api/v1/files/id \
--header 'Authorization: Bearer $API_KEY' \
--header 'X-Workspace-Key: X-Workspace-Key'Path parameters
idstringrequiredA file id (digits) or a folder id (uuid)
Query parameters
confirm_delete_transfersbooleantrue to also delete the transfers that hold the item (only the exact text true counts)
workspace_keystringThe same key as the X-Workspace-Key header, for clients that cannot set headers. Send one of the two, or both with the same value (different values are 400 conflicting_workspace)
Header parameters
X-Workspace-KeystringrequiredThe 8-character key of the workspace this call acts on; GET /workspaces lists the keys a token can use. A workspace id is refused (400 workspace_key_required)
Idempotency-KeystringMakes a write safe to repeat. Send a random value (a UUID is fine) of up to 255 visible characters. A repeat of the same request gets the first answer again, with the header `Idempotent-Replayed: true`, and does nothing twice. The same key for a different request is 422 `idempotency_key_reused`; the same request while the first one is still running is 409 `idempotency_in_progress`. A 5xx or 429 is not remembered, so retrying it runs the request again. Keys last 24 hours and belong to the account that created the token.