Get a handoff
GET
Get a handoff
Authorizations
Path Parameters
Response
Successful Response
The API-response shape for a single handoffs row (UI + channel runtime).
Available options:
requested, assigned, accepted, resolved, cancelled Available options:
workflow_terminal, router, policy The complete, enriched handoff packet — the channel-runtime contract.
Two halves, by who fills them:
- engine-supplied intent (rides on the
handoffsignal):reason,static_text,context_vars. - service-enriched at record time (needs DB access —
packet.py):summary(fromconversations.summary) andtranscript_ptr.
Previous
Relay an operator message on a handed-off conversationPersist an OUTBOUND operator message (§6.4.1) then deliver it.
Persists a ``role='assistant'`` ``ConvMessage`` attributed to the relaying
operator (``authored_by='human_operator'`` + ``operator_actor_id``),
soft-claims the handoff if unassigned, then hands the already-persisted row
to the channel delivery adapter (the adapter never mints a new message).
Next
Get a handoff