HTTP endpoints
HTTP: tasks
All 3 tasks endpoints, with request fields and access notes.
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/tasks
List tasks.
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): channel, detail, parent_id, room_id, status, thread_id.
GET /v1/tasks/{id}
Get task.
Path parameters: id.
Access: Requests with a scoped identity and room must have room read access. Additional permissions may apply.
This directory does not provide a request schema for this endpoint. Use the corresponding supported tool or client where available.
POST /v1/tasks/{id}/complete
Task complete.
Path parameters: id.
Access: 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.