Reference
API reference
Authenticate and pull context programmatically.
Authentication
Create a workspace API key under Settings → API keys and send it as a Bearer token. It acts for the whole organization and carries no personal role, so it can read and write context but not, for example, change billing.
bash
curl https://<your-ctx-backend>/v1/tickets/OPS-102/context \
-H "Authorization: Bearer ctx_..."Core endpoints
- GET /v1/meetings — recently captured meetings.
- GET /v1/meetings/:id/bundle — the latest bundle for a meeting.
- POST /v1/ticket-plans — draft an epic and stories from a bundle.
- POST /v1/ticket-plans/:id/dry-run — what a push would create, and what blocks it.
- POST /v1/ticket-plans/:id/push — create or update the Jira issues; never duplicates.
- GET /v1/tickets/:key/context, GET /v1/bundles/:id/markdown, GET /v1/context/search?q= — read context back by ticket, by bundle, or by search.
- POST /v1/mcp — the same context, as an MCP server (see Cursor & Claude).
Every route here also accepts the same Bearer session a signed-in person uses, which is what the dashboard itself calls.