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, but all of them are created and managed from the same place in the eCourtDate Console.
Use this page to work out which API you need, 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 |
| PDFs API (Document Generation) | Generates court-ready PDFs from versioned templates with merge tags, or from one-off layouts | https://api.pdfs.ecourtdate.com/v1 | PDFs API and docs.pdfs.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 |
| Chatbots API | Self-service chatbots for websites and messaging channels | Not yet published | Not yet published | Coming soon |
Platform API vs. standalone APIs
The platform API is included with your eCourtDate agency account. It reads and writes the records your 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 with its own subscription. It runs on its own hostname, is documented on its own site, and does not require an eCourtDate agency account to use. You can call a standalone API on its own, or alongside the platform API in the same integration.
Getting API credentials
Credentials for every eCourtDate API are created in the eCourtDate Console under APIs at console.ecourtdate.com/apis.
- Sign in to the eCourtDate Console.
- 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.
The step that lets you choose which API a client belongs to is rolling out alongside the standalone API products. If you do not see it yet, open a support ticket in the Console using the Help button in the bottom-right corner and ask for a client on the API you need.
The credential type differs by API, so check the documentation for the API you are integrating 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} |
| PDFs API | A scoped API key | x-api-key: {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, Citations, and Chatbots 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.