eCourtDate APIs
eCourtDate offers the platform API, which covers the core justice data model, plus a set of standalone APIs licensed as separate products. Each standalone API has its own base URL, its own documentation site, and its own credentials.
Use this page to work out which API applies, then follow the link to its documentation.
Available APIs
| API | What it does | Base URL | Documentation | Status |
|---|---|---|---|---|
| Platform API | Clients, events, contacts, messages, payments, cases, check-ins, and flows | https://api.ecourtdate.com (multi-region), plus per-region URLs | API Guide and API Reference | Available |
| Doc Gen API (Document Generation) | Generates print-ready justice agency PDFs from versioned templates with merge tags, or from one-off layouts | https://api.pdfs.ecourtdate.com/v1 | Doc Gen API and docs.pdfs.ecourtdate.com | Available |
| Chatbots API | Answers questions from an agency-controlled knowledge base and returns the sources it used, over an OpenAI-compatible API | https://api.chatbots.ecourtdate.com/v1 | Chatbots API and docs.chatbots.ecourtdate.com | Available |
| Warrants API | Electronic warrant management for law enforcement and courts | Not yet published | Not yet published | Coming soon |
| Citations API | Electronic citation issuance, tracking, and court integration | Not yet published | Not yet published | Coming soon |
Platform API vs. standalone APIs
The platform API is included with the eCourtDate agency account. It reads and writes the records the agency already manages in eCourtDate: clients, events, contacts, messages, payments, cases, check-ins, and flows. Start with the API Guide for authentication, rate limits, pagination, and error handling, then use the API Reference for per-resource endpoint detail.
A standalone API is a separate product, purchased as a paid add-on to the eCourtDate account. It runs on its own hostname and is documented on its own site, but its keys are created and managed in the eCourtDate Console alongside the platform API credentials. A standalone API can be called on its own, or alongside the platform API in the same integration.
Getting API credentials
Credentials for the platform API, the Doc Gen API, and the Chatbots API are all created in the eCourtDate Console under APIs at console.ecourtdate.com/apis. Key management is self-service: keys are create, scope, rotate, and revoke keys directly from that page.
The Doc Gen API and the Chatbots API are paid add-ons. Buying the add-on is the first step, and the eCourtDate help team then activates it on the account. Until that activation is done, the API does not appear as a choice on the APIs page and no key can be issued for it.
- Purchase the add-on for the API required. The platform API is included with the eCourtDate agency account and needs no add-on.
- Wait for the eCourtDate help team to activate the add-on on the account. To ask about an add-on or check on activation, open a support ticket in the Console using the Help button in the bottom-right corner.
- Sign in to the eCourtDate Console and go to APIs.
- Create a new API client, and select which API the client is for.
- Copy the credentials that are issued. Store them in a secrets manager, never in source control or client-side code.
Purchasing an add-on does not switch the API on by itself. The eCourtDate help team activates it, and only then does that API become selectable on the APIs page. If an add-on has been purchased and the API still does not appear, open a support ticket in the Console using the Help button in the bottom-right corner.
The credential type differs by API, so check the documentation for the API being integrated with:
| API | Credential issued | Sent as |
|---|---|---|
| Platform API | client_id and client_secret, exchanged for a Bearer token through the OAuth2 client credentials flow | Authorization: Bearer {access_token} |
| Doc Gen API | A scoped API key | x-api-key: {key} |
| Chatbots API | A scoped API key | Authorization: Bearer {key} |
For a comparison of eCourtDate authentication methods, including OAuth and SSO for user-facing applications, see the Authentication Overview. For the platform API token exchange in detail, see API Authentication.
Early access
The Warrants and Citations APIs are not generally available yet. To ask about early access or timelines, open a support ticket in the Console using the Help button in the bottom-right corner.