API Reference

Source of truth#

The running FastAPI backend exposes generated API reference pages:

http://localhost:5678/docs
http://localhost:5678/redoc

Use those generated pages for endpoint schemas because they are produced from the live route definitions.

Main route families#

The backend mounts most routes under /api/v1, including auth, users, matters, participants, records, blueprints, workflows, workflow execution, human tasks, matter tasks, documents, templates, notes, audit, dashboard, workspaces, settings, Gmail, Telegram, Nango integrations, webhooks, tools, notifications, chat, commands, analytics, usage, billing, support, follow-up tasks, and admin billing.

The non-versioned health routes are:

GET /health
GET /health/aggregate
GET /health/stream

Matter-scoped human-task routes use {matter_reference_id}:

GET /api/v1/matters/{matter_reference_id}/feedback-tasks
POST /api/v1/matters/{matter_reference_id}/tasks/{task_id}/submit-feedback

No public SDK#

This repository does not include a maintained public SDK package. Keep docs language to "API reference" and examples using HTTP, curl, or local frontend API adapters.

Use stable contracts#

External callers should favor explicit matter payloads, workflow IDs, task IDs, idempotency keys where routes support them, and workspace-scoped authentication. If an operation would normally emit audit history or alter legal workflow state in the UI, API-triggered behavior should preserve that same reviewability.

The API does not expose court, docket, or case-law integrations.