Errors
HTTP error shapes and common failure modes.
All API errors use a consistent JSON shape with a stable code, message, and request_id.
Error shape
{
"error": {
"code": "contact_not_found",
"message": "Contact was not found for this project.",
"request_id": "hostname/abc123-000001"
}
}request_id matches the X-Request-Id response header. Quote it when contacting support. The Node SDK exposes it as ComRaidError.requestId; the mobile SDKs do not surface it yet, so read the X-Request-Id header if you call the Mobile API directly.
Status codes
| Status | Meaning |
|---|---|
| 400 | Invalid request |
| 401 | Missing or invalid authentication |
| 403 | Authenticated but not allowed |
| 404 | Resource not found in this project, or no route matched (not_found) |
| 405 | Method not allowed for this path (method_not_allowed; Allow lists accepted methods) |
| 409 | Idempotency or uniqueness conflict |
| 422 | Valid JSON but invalid domain operation |
| 429 | Rate limited (Retry-After may be set) |
| 500 | Internal error (internal_error) |
| 503 | Service temporarily unavailable |
Common codes
not_found— unknown path, or a resource was not found in this project.method_not_allowed— the path exists but not for this HTTP method; check theAllowheader.internal_error— unexpected server failure (including recovered panics).contact_not_found— single-recipient send with unknown Contact.no_active_endpoints— no delivery could be created.idempotency_conflict— same key, different body.idempotency_in_progress— first request still running.rate_limited— request exceeded an operational rate limit; honorRetry-After(seconds) when present. See Rate limits.