Skip to main content

Tyler Odyssey / Enterprise Justice (API)

This integration connects Tyler Technologies' Odyssey or Enterprise Justice case management system with eCourtDate using the Odyssey REST API. eCourtDate automatically syncs party, case, and hearing data on a recurring schedule, enabling automated court date reminders, payment notifications, and other communications.

Who Is This For?​

This integration is designed for agencies that meet all three criteria:

  1. Use Odyssey or Enterprise Justice as their case management system.
  2. Have licensed the API Toolkit from Tyler Technologies.
  3. Have their CMS hosted in a cloud (SaaS) environment. On-premises deployments require a different approach — see On-Premises Hosting below.

How It Works​

  1. Scheduled sync — eCourtDate calls the Odyssey API on a recurring basis (hourly or nightly, configurable per agency) to retrieve party, case, and hearing data.
  2. Secure data transmission — All API calls use encrypted connections that meet CJIS security standards.
  3. Automatic processing — eCourtDate maps the API response data to Clients, Events, Contacts, and Cases.
  4. Automated messaging — Notifications are sent based on the agency's configured messaging flows and templates.

This is a unidirectional integration. eCourtDate reads data from Odyssey but does not create or modify records in the CMS.

Odyssey API Endpoints Used​

The integration uses the following Odyssey API endpoints:

EndpointPurpose
FindPartiesRetrieves party details including defendants, witnesses, and attorneys.
FindCaseRetrieves case details and statuses.
GetScheduledHearingsByPartyIDFetches upcoming court dates, times, and locations for a given party.

Data Included​

The following data is transferred from Odyssey to eCourtDate during each sync:

FieldDescription
Party IDUnique identifier for the party in Odyssey.
First Name / Last NameParty name.
Party DescriptionRole in the case (defendant, witness, attorney, etc.).
Preferred LanguageLanguage preference for notifications.
Phone / EmailContact information for message delivery.
Event Date and TimeScheduled hearing date and time.
Event StatusCurrent status of the hearing.
Location NameWhere the hearing takes place.
Judge NameAssigned judge.
Case NumberOfficial case number.
Payment StatusPayment information (if available).
Attorney DetailsAttorney assignments (if included).
Case FinesFine amounts (if included).

Including Additional Data​

Depending on data availability in your Odyssey instance, additional information can be included:

  • Attorney assignments and contact details
  • Case fines and payment statuses
  • Custom data fields based on agency needs

Contact the Help Center to discuss what additional data your agency requires.

Prerequisites​

Before setting up this integration:

  1. Confirm API licensing — Contact your Tyler Technologies Client Success Manager to verify your API Toolkit licensing status. Tyler Technologies may charge separately for API access depending on your licensing agreement.
  2. Confirm cloud hosting — This integration requires a cloud-hosted (SaaS) Odyssey or Enterprise Justice instance. See On-Premises Hosting if your CMS is hosted locally.
  3. Assign IT resources — Although no custom development is required, your IT team needs to create API credentials in Odyssey and update any network or firewall settings to allow eCourtDate access.

Setup Steps​

  1. Confirm API access with your Tyler Technologies representative. Verify licensing and any associated costs.
  2. Create a staging agency in eCourtDate (if you do not already have one). See Staging and Production.
  3. Configure API credentials in the staging agency. Enter the Odyssey API endpoint URL and authentication details provided by Tyler Technologies.
  4. Validate data — Confirm that records created or updated in Odyssey are reflected in the eCourtDate staging agency. We recommend validating for at least one week before going live.
  5. Configure messaging flows — Set up notification templates and delivery rules for the data being synced.
  6. Review generated messages in the Console to confirm notifications match expectations.
  7. Go live — Once validated, copy the configuration to your production agency and enable the recurring sync schedule.

Sync Frequency​

The API integration supports hourly or nightly sync schedules, configurable per agency. Hourly sync is recommended for agencies that need near-real-time updates. The sync schedule can be adjusted at any time through the Console.

On-Premises Hosting​

The direct API integration is only available for agencies with cloud-hosted (SaaS) Odyssey or Enterprise Justice instances. If your CMS is hosted on-premises, consider one of these alternatives:

  • SFTP integration — Use the SFTP-based integration with nightly ECR exports.
  • Middleware approach — Implement a middleware layer that reads from your local Odyssey instance and pushes data to eCourtDate via the REST API. This requires custom development by your IT team.

Frequently Asked Questions​

How long does the integration take to set up? Once API credentials are configured, the integration is immediately available in staging. We recommend verifying data accuracy for at least one week before going live.

Does eCourtDate write data back to Odyssey? No. This is a unidirectional integration. Data flows from Odyssey into eCourtDate. eCourtDate does not create or modify records in the CMS.

Do we need developers on our team? No custom development is required. Your IT team needs to create API credentials in Odyssey and configure network access, but the eCourtDate side is configured through the Console.

What happens if the Odyssey API is temporarily unavailable? eCourtDate retries failed sync attempts automatically. If the API remains unavailable, the next scheduled sync picks up any missed data. No records are lost.

Can we use both the SFTP and API integrations at the same time? Yes. Some agencies use the API integration for frequent updates and supplement with SFTP for bulk historical imports or data that is not available through the API endpoints.