Explore the documentation
Start
Take one application from an empty draft to a signed warrant, then learn the API key model, actor attribution, and the conventions every request shares.
Getting started →Warrants
The four states and every transition between them: submitting, routing to a judge, signing, rejecting, reopening, comments, edit locks, and public links.
Warrant lifecycle →Templates and files
The form definitions applications are built from, the field types they declare, the rendered court document, and the presign, upload, confirm flow for attachments.
Templates →Administration
Members and the four built-in roles, custom roles from the permission catalog, locations, agency routing and escalation, and the audit trail.
Users and roles →Built for production
A workflow, not just endpoints
Four states and a fixed set of transitions, so an application is never in an ambiguous place. Warrant lifecycle
Every action attributed
Writes carry X-On-Behalf-Of, so the audit trail names the person, not the integration. Audit trail
Templates drive the data
Read a template's elements and build form_data from it, so a form change does not break your client. Form elements
Errors you can program against
One envelope, {"error": {...}}, with a stable code, a type, and the offending param. Errors
Resources
- Interactive API reference: every endpoint, request, and response, with a try-it console.
- OpenAPI specification: the machine-readable contract, also published as YAML; generate clients in your language.
- AI agents: a copy-paste briefing prompt, plus llms.txt for tools.
- eCourtDate.com: API keys are issued and activated for your agency by eCourtDate.