Skip to main content

Rate Limits

Rate limits restrict how many API requests you can make within a given time period. They exist to protect the platform from being overwhelmed and to ensure fair access for all agencies. Each API request — whether it's fetching data, creating a record, or sending a message — counts toward your limit.

eCourtDate enforces rate limits to ensure platform stability and fair usage across all clients.

Default Limit​

The default rate limit is 1,000 requests per minute per API client. Contact support if you are on a Dedicated plan and require a higher limit.

Rate Limit Responses​

HTTP 429 Too Many Requests​

You have exceeded the rate limit. Wait a minimum of 1 minute before retrying.

HTTP 409 Conflict (Duplicate Detection)​

A duplicate message was detected within the 30-minute deduplication window. To resolve this:

  • Set skip_duplicate=true to bypass duplicate checking entirely.
  • Set scheduled_at to more than 30 minutes from the previous message.
  • Use the duplicate_buffer or duplicate_interval parameters to customize the deduplication window.
  • Wait 30 or more minutes before sending the same content.
  • Ensure each message has unique content.

See Idempotency & Deduplication for more details.

HTTP 503 Service Unavailable​

The API is temporarily unavailable. Retry after 1 minute.

HTTP 504 Gateway Timeout​

A network issue occurred between services. Retry after 1 minute.

Use exponential backoff for transient errors (429, 503, 504):

  1. First retry after 1 second.
  2. Second retry after 2 seconds.
  3. Third retry after 4 seconds.
  4. Stop after 3 retries and log the failure for investigation.