Transfer an attention card to a different person
/api/companies/{companyId}/attention/{sourceKind}/{sourceId}/transferTransfer an attention card to a different person.
Requires a member with organization write access. Routes the card to another person ("Route to @x"): they become its addressee, so it joins their For you view and only they may answer it. The new owner must be able to answer requests on the task (422 otherwise). Only issue_thread_interaction cards can be transferred (422 otherwise); chat questions stay with the person in the chat (422); a runnable agent's request or an answered card returns 409; routing to the current addressee returns alreadyTransferred=true. Writes an attention.transferred activity entry.
Authorization
Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. How keys work.
Path parameters
Request body
application/json · required
1–200 charactersat most 4000 charactersResponses
details names each field that failed.Errors return {"error": "..."}, often with a code and details. See errors and limits.