Environments & Regions

eCourtDate operates across multiple environments and geographic regions. Each agency is assigned a specific region during onboarding. This page describes every available environment, how they differ, and how to select the right base URL for your integration.

Available Environments

Environment	Base URL	Purpose
Staging	staging.api.ecourtdate.com	Testing and development. Outbound messages, data reporting, and payment processing are simulated.
US East	us-east.api.ecourtdate.com	Production -- US East region.
US West	us-west.api.ecourtdate.com	Production -- US West region.
US South	us-south.api.ecourtdate.com	Production -- US South region.
US Texas	us-texas.api.ecourtdate.com	Production -- US Texas region.
Multi-Region	api.ecourtdate.com	Production -- routes to the appropriate regional endpoint automatically.

Staging vs. Production

The staging environment is functionally identical to production with the following exceptions:

• Outbound messages are simulated. SMS, email, and voice messages are created and tracked in the system but are never delivered to recipients. This lets you test message flows safely without contacting real people.
• Data reporting is simulated. Reports and analytics reflect test data only and do not count toward production metrics.
• Payment processing is simulated. Payment transactions are processed in sandbox mode. No real charges are made and no funds are transferred.

Everything else -- authentication, API endpoints, request/response schemas, webhooks, SFTP -- behaves identically to production. This makes staging an ideal environment for developing and validating integrations before going live.

Region Assignment

Your agency's production region is assigned during initial setup based on factors such as geographic location and data residency requirements. You can find your assigned region in the eCourtDate Console under your agency settings.

If you are unsure which region your agency uses, contact help@ecourtdate.com.

Multi-Region Endpoint

The api.ecourtdate.com endpoint acts as a multi-region gateway. Requests sent to this URL are automatically routed to the correct regional endpoint based on your agency's configuration. This is useful when you want a single base URL that works regardless of region, although using the direct regional URL may offer marginally lower latency.

Choosing a Base URL

• During development and testing, always use staging.api.ecourtdate.com.
• In production, use your assigned regional URL (e.g., us-east.api.ecourtdate.com) for the lowest latency, or use api.ecourtdate.com for automatic routing.