Accept a pending handoff

POST/v1/chats/{chat}/handoff/accept

Take a pending handoff live (human_pending → human). Auth stays the partner’s API key: the human actor is honest about the role, not an authenticated person. When the accept is made through our agent console with a named operator, the event log records WHICH human accepted it (operator on the events read).

Behavior

Legal only from human_pending. Once applied, the chat is human, and a second accept returns HTTP 409 code 2025.
Two accepts arriving together resolve to one; first writer wins, and the loser records nothing, so the transcript never shows an accept that did not take effect.
When our console attributes the accept to a named operator, that operator claims the chat (assigned_operator); a different operator accepting the same entry returns HTTP 409 code 2009, naming the holder. The claim is released when the chat returns to your system (POST …/handoff with to: "partner"), which is also how a claim held by someone unreachable is cleared: return it, then accept it again.
A claim does not restrict sending; the desk is shared at the brand level.

Path ParametersExpand Collapse

chat: string

Body ParametersJSONExpand Collapse

reason: optional string

Free-text reason, recorded on the ownership event.

ReturnsExpand Collapse

ok: true

Accept a pending handoff

curl https://messages.api.linqapp.com/v1/chats/$CHAT/handoff/accept \
    -X POST \
    -H "Authorization: Bearer $LINQ_AMB_API_KEY"

{
  "ok": true
}

Returns Examples

{
  "ok": true
}