Skip to main content

Error Catalog

Complete error reference for eCourtDate.

HTTP Status Codes

CodeNameDescriptionAction
400Bad RequestInvalid request body or missing required parametersValidate request body; check required fields
401UnauthorizedInvalid or expired Bearer tokenRe-authenticate; verify API client is not revoked
403ForbiddenAgency inactive or insufficient permissionsConfirm agency is active; use API client token (not user token)
404Not FoundResource or endpoint not foundCheck endpoint path; if "Agency Not Found", configure Default Agency
405Method Not AllowedWrong HTTP methodUse correct method (GET/POST/PATCH/DELETE)
409ConflictDuplicate message detected (30-min window)Use skip_duplicate=true, adjust scheduled_at, or use duplicate_buffer
429Too Many RequestsRate limit exceeded (1000 req/min default)Wait 1 minute; implement exponential backoff
500Internal Server ErrorServer-side errorContact support with request details
503Service UnavailableAPI temporarily unavailableRetry after 1 minute
504Gateway TimeoutNetwork timeoutRetry after 1 minute

Carrier Error Codes

Carrier-specific errors occur when a message cannot be delivered by the telecommunications carrier. These are returned in message delivery status updates.

Error codes and reasons are maintained as JSON files:

Common Carrier Error Categories

  • Unreachable/Undeliverable: Recipient number invalid, disconnected, or out of service
  • Blocked/Filtered: Message blocked by carrier spam filter or recipient block list
  • Capacity: Carrier network congestion or volume limits
  • Timeout: Delivery attempt timed out
  • Format: Message format not supported by carrier

Message Retry Behavior

  • Automatic retry for: temporary network issues, temporary spam blocks, volume limits, carrier/gateway issues
  • Messages stop retrying 24 hours after original send time
  • Event-linked messages stop if the event date passes