GitDocket
GitDocket docs
Local HTTP reference.
Inspect the data used by the local web interface. For automation, start with the CLI or MCP tools.
About these routes
docket serve provides these routes for its local web interface. They may change between versions, and there is no published OpenAPI specification.
The MCP input schemas are the available machine-readable tool reference. For HTTP inspection, use the loopback URL printed by Serve on your own computer.
Useful read routes
All routes below use GET. Task, epic, document, and search responses include a page object. The board keeps pagination inside its columns.
| Route | Returns |
|---|---|
/api/nav?summary=1 | Navigation summary. |
/api/home?briefing=1 | Home briefing. |
/api/tasks?page=1&limit=20 | Paginated work items. |
/api/board?page=1 | Work grouped by state. |
/api/epics?page=1 | Epic rollups. |
/api/docs?page=1 | Document inventory. |
/api/search?q=welcome&page=1&limit=10 | Ranked search hits. |
/api/source/reference/welcome.md | A bounded Markdown source page. |
The source example exists in the Harbor demo. Use an exact path from your own bundle inventory. Source responses include a hash and may include a continuation cursor; unknown paths return 404 and stale cursors return 409.
Try a read
From an initialized project directory, start the local server on an available port:
docket serve --port 4111Leave that server running. In a second terminal, query the same port:
curl 'http://127.0.0.1:4111/api/tasks?page=1&limit=20'Serve binds to loopback and checks the request host and origin. It has no remote authentication layer; it is intended for same-computer use. This page covers a small read subset. Use the CLI or MCP operations for documented task mutations.