Error codes

Error response shape

All EchoCue API errors share the same envelope. The error_code sits directly inside data, alongside any context-specific fields the endpoint provides:

{
  "status_id": 4xx | 5xx,
  "message":   "Human-readable summary",
  "data": {
    "error_code": 132001,                  // Meta or EchoCue code (string or number)
    // ... endpoint-specific context fields below ...
    "can_send_freeform": false,            // example: WhatsApp 24h-window failures
    "can_send_template": true,
    "available_templates": [ ... ]
  }
}

Branch your client logic on data.error_code - the canonical identifier. The message field is human-readable copy for logs and UI surfacing; it can change without notice.

For WhatsApp send failures, error_code mirrors Meta's WhatsApp Cloud API code so you can cross-reference the official Meta documentation if needed.

Permanent vs retryable

EchoCue's notification worker auto-retries some failures and gives up on others. The classification:

• Retryable. Transient failures (rate limit, network blip, server overload). EchoCue retries a few times with backoff before giving up.
• Permanent. Will not succeed on retry no matter how many times we try (invalid recipient, missing template, format mismatch). EchoCue marks the notification as failed, refunds the credit, and stops.