eCourtDate Electronic Warrants API guides
The eCourtDate Electronic Warrants API is the programmatic interface to the eCourtDate electronic warrant workflow. An application is drafted from a template, submitted for review, routed to a judge, and then signed or rejected. Every action is written to an immutable audit trail, and the signed result is rendered as a court-ready document.
These guides explain the concepts and the workflows; the interactive API reference documents every endpoint, request, and response, and includes a try-it console.
Base URL: https://api.warrants.ecourtdate.com/v1
Start
- Getting started: your first application, from draft to signed.
- Authentication: API keys, scopes, and actor attribution.
- Conventions: identifiers, timestamps, paging, and the rules every request shares.
Warrants
- Warrant lifecycle: the four states and every transition between them.
- Creating applications: choosing a template and filling in its fields.
- Reviewing and signing: the review queue, routing, signing, and rejection.
- Comments: the thread on an application, including internal notes.
- Locking: editing safely when several people work the same application.
- Trash and restore: reversible removal, and permanent deletion.
- Public links: publishing a signed warrant for someone without an account.
Templates and files
- Templates: the form definitions applications are built from.
- Form elements: the field types a template declares and how they map to
form_data. - Generated documents: the rendered warrant, document styles, and regeneration.
- Files and attachments: the presign, upload, confirm flow.
Administration
- Users and roles: the four built-in roles, custom roles, and the permission catalog.
- Locations: the facilities and courts applications refer to.
- Agency settings: routing, escalation, and which templates are available.
- Audit trail: what is recorded and how to read it back.
Reliability and operations
- Errors: the error envelope and the registry of every code.
- Rate limits: the limits, the headers, and how to back off.
- Security: key handling, agency isolation, and how warrant contents are protected.
- Versioning: what is stable, what can change, and how deprecation works.
Resources
- AI agents: a copy-paste briefing for coding assistants, and
llms.txt.