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…
Change a transfer: view only, expiry or password
Changes a plain transfer after it was made. view_only false lets the people it was delivered to download its files in their client portal; true takes that back. expires_at (a future date at most three years ahead, or null to remove) and password (4 to 100 characters, or null to remove) follow the app's own transfer settings rules. A paid transfer is refused (409 conflict): its payment stays the gate. Answers the transfer as getTransfer does. Needs transfers:create.
What you provide
- View onlyoptional: false: the people the transfer was delivered to can download its files. true: they can only view them
- Expires atoptional: A future date at most three years ahead, or null to remove the expiry
- Passwordoptional: 4 to 100 characters, or null to remove the password. Never returned
Do this with AI
I want to change a transfer: view only, expiry or password. Use the Tarkle API. Read the reference for this operation and follow it exactly: https://project-03b42162.restlessdocs.com/endpoint/updatetransfer.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/transfers/{id}curl --request PATCH \
--url https://tarkle.com/api/v1/transfers/id \
--header 'Authorization: Bearer $API_KEY' \
--header 'Content-Type: application/json' \
--header 'X-Workspace-Key: X-Workspace-Key' \
--data '
{
"view_only": true,
"expires_at": "2024-01-01T00:00:00Z",
"password": "password"
}
'Path parameters
idstringrequiredA transfer id, from createTransfer's answer
Query parameters
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.
Body
application/jsonrequiredview_onlybooleanfalse: the people the transfer was delivered to can download its files. true: they can only view them
expires_atstring · date-time | nullA future date at most three years ahead, or null to remove the expiry
passwordstring | null4 to 100 characters, or null to remove the password. Never returned