Integrations
eCourtDate offers pre-built integrations with third-party case management systems and platforms. These integrations automate data transfer so agencies do not need to build custom connections from scratch.
Available Integrations
| Integration | Method | Description |
|---|---|---|
| Tyler Odyssey / Enterprise Justice (SFTP) | SFTP | Nightly delivery of the eCourtDate court reminder ECR (upcoming hearings and party contact details) from Odyssey or Enterprise Justice to the court's SFTP server, retrieved by eCourtDate every hour. |
| Tyler Odyssey / Enterprise Justice (API) | API | Hourly sync of upcoming hearings, case parties, and their phone numbers and email addresses from Odyssey through the TranslationBridge External Service, with an optional outcome report pushed back to the case. |
| i3 Verticals CourtOne (SFTP) | SFTP | Nightly delivery of a CourtOne hearing export (upcoming hearings, party contact details, and case numbers) to an eCourtDate managed SFTP server on AWS GovCloud, mapped by the prebuilt i3 Verticals file template. |
| Neumo Jury (API) | API | Send ad-hoc text messages to jurors from Neumo Jury, using eCourtDate as the texting service. |
| ReportBeam (FTP) | Secure FTP | Scheduled sync of field-issued citations from a ReportBeam file server into eCourtDate citations, clients, cases, court events, and payments. |
| Microsoft Graph | API | Scheduled sync of Microsoft Entra ID users into eCourtDate Clients and work Contacts through Microsoft Graph, with group and domain filters and organization audiences. |
How Integrations Work
All pre-built integrations follow the same general pattern:
- Data is pulled from the source system into eCourtDate on a recurring schedule (nightly, hourly, or on-demand depending on the method).
- eCourtDate processes the data and creates or updates Clients, Events, Contacts, Cases, and other records.
- Automated messaging flows generate notifications based on the synced data and the agency's configured templates.
The Microsoft Graph integration is narrower: it creates and updates Clients, their work Contacts, and their organization memberships, can archive the Clients of users who leave, and does not trigger auto messages.
Integrations are unidirectional: data flows into eCourtDate from the source system. eCourtDate does not write back to or modify records in external systems, with one opt-in exception: the Tyler Odyssey API integration can file an outcome report on each case.
Staging First
We recommend testing every integration in a staging agency before going live. This allows validate data accuracy, review generated messages, and confirm notification settings without affecting production.
Need a Custom Integration?
If the system is not listed above, eCourtDate supports custom integrations through SFTP, the REST API, and webhooks. Vendors and system integrators that build their own connection start with Build an Integration, which has guides for case management systems and for kiosks and lobby displays. Open a support ticket in the Console using the Help button in the bottom-right corner for guidance on connecting the system.