CourtPath

Last action

Every visible action is executed through /api/v1. Product status is shown here; the raw API response is available only when technical traceability is needed.

No operation has run yet.

Technical API response

Use this for audit/debug review. The workflow should be understandable without reading JSON.

Responses render here.

Developer API context

These fields drive the web shell and prove the same API contract can be reused by mobile clients.

Role context is an audit/development control. Production sessions should use Supabase Auth claims instead of local role switching.

API user Roles Supabase bearer token Matter ID Court ID Packet ID Upload ID Asset ID Filing ID Workspace ID Item or target ID Plan or workbench ID Reviewer MFA Search query

Intake notes Evidence description Packet title IP asset name IP asset description Team invite email Checkout type Checkout amount cents

CourtPath Assistant

Ask about the active deadline, evidence gap, filing packet, IP asset, billing state, or review gate.

Workspace question