Email error codes
Email acceptance errors, HTTP statuses, retry guidance, and post-acceptance failure reasons.
This page lists email acceptance errors and post-acceptance failure reasons. Success requires both HTTP 202 and code=000000; acceptance does not mean delivery.
Acceptance errors
Use the HTTP status and six-digit code to decide what to do. Keep the traceId for support; do not branch on the human-readable message.
On failure, data=null. message is dynamic and should not be the only decision criterion.
| HTTP | code | Meaning and action |
|---|---|---|
| 400 | 010001 | Malformed JSON or request body. |
| 400 | 010002 | A required non-idempotency header is missing. |
| 400 | 010003 | Field, business parameter, or X-Custom-TraceId validation failed. |
| 400 | 010013 | Idempotency key is missing or invalid. |
| 405 | 010009 | HTTP method not supported. |
| 415 | 010010 | Content-Type not supported. |
| 401 | 020001 | AppID or API Key is missing. |
| 401 | 020002 | API Key is invalid, unknown, or disabled. |
| 401 | 020008 | Signature headers are incomplete, the signature is wrong, or Nonce was replayed; regenerate and check credentials. |
| 401 | 020009 | CurTime has a valid format but is outside the window; synchronize the clock and re-sign. |
| 403 | 020005 | Egress IP is not allowed or the allowlist configuration is invalid. |
| 409 | 010007 | The idempotency key maps to different content; stop automatic retries. |
| 409 | 010008 | The original task is still processing; use limited backoff with the original key and body. |
| 403 | 030003 |
Last updated on