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…
Deliver a transfer to contacts' client portals
Adds contacts of this workspace to a plain transfer's recipients, so it appears in their client portal. Sending ids that are already there changes nothing. No email is sent. A contact sees it only while their portal access is on (setContactPortalAccess). A view-only transfer shows its files in the portal without downloads until updateTransfer sets view_only false. A paid transfer is refused (409 conflict). Needs transfers:create; the token's creator must be allowed to share transfers and see contacts.
What you provide
- Contact ids: Contact ids from createContact's or listContacts' answer
Do this with AI
I want to deliver a transfer to contacts' client portals. Use the Tarkle API. Read the reference for this operation and follow it exactly: https://project-03b42162.restlessdocs.com/endpoint/delivertransfertocontacts.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}/contactscurl --request POST \
--url https://tarkle.com/api/v1/transfers/id/contacts \
--header 'Authorization: Bearer $API_KEY' \
--header 'Content-Type: application/json' \
--header 'X-Workspace-Key: X-Workspace-Key' \
--data '
{
"contact_ids": [
"3fa85f64-5717-4562-b3fc-2c963f66afa6"
]
}
'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/jsonrequiredcontact_idsstring · uuid[]requiredContact ids from createContact's or listContacts' answer