HTTP endpoints

HTTP: handoffs

All 2 handoffs endpoints, with request fields and access notes.

On this page

POST /v1/handoffs
GET /v1/handoffs/{room_id}

Request fields and access notes below are partial. Additional constraints and permissions may apply. Prefer the corresponding MCP tool and schema where available.

POST /v1/handoffs

Create handoff.

Access: LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply.

Request body fields (partial)

Field	Type	Required	Constraints
`project_id`	string	yes	See operation notes.
`name`	string	yes	See operation notes.
`prose_body`	string	yes	See operation notes.
`source_room_id`	string	no	See operation notes.
`descendant_handle`	string	no	See operation notes.
`invite_ttl_sec`	integer	no	See operation notes.
`by_agent_id`	string	no	See operation notes.
`topic`	string	no	See operation notes.
`metadata`	object	no	See operation notes.
`ancestor_preferred_harness`	string	no	See operation notes.
`descendant_preferred_harness`	string	no	See operation notes.
`acl_override`	object	no	See operation notes.

Other constraints may apply, including for fields marked optional.

GET /v1/handoffs/{room_id}

Get handoff.

Path parameters: room_id.

This directory does not provide a request schema for this endpoint. Use the corresponding supported tool or client where available.