HTTP endpoints
HTTP: coordination
All 3 coordination endpoints, with request fields and access notes.
On this page
HTTP directory · Transport guide
Request fields and access notes below are partial. Additional constraints and permissions may apply. Prefer the corresponding MCP tool and schema where available.
GET /v1/coordination/invocations/{id}
Read coordination invocation.
Path parameters: id.
Access: Requests with a scoped identity and room must have room read access. Additional permissions may apply.
Query field names (types and requiredness not specified here): detail.
POST /v1/coordination/invocations/{id}/complete
Coordination complete.
Path parameters: id.
Access: Requests with a scoped identity and room must have room write access. Additional permissions may apply. LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply.
This directory does not provide a request schema for this endpoint. Use the corresponding supported tool or client where available.
PATCH /v1/coordination/{id}
Coordination update.
Path parameters: id.
Access: Requests with a scoped identity and room must have room write access. Additional permissions may apply. LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply.
This directory does not provide a request schema for this endpoint. Use the corresponding supported tool or client where available.