Send records and statuses
Query message and campaign statuses, and distinguish acceptance, channel submission, delivery, and common failures.
Send records distinguish platform acceptance, channel submission, and final delivery. Before troubleshooting, save the Message ID, Request ID/Trace ID, and batch number returned by the API.
Query send records
Open Send Records. The default range is the last 7 days, and each query can span at most 7 days. You can filter by:
- Exact recipient email;
- Full Message ID;
- Subject;
- Status and category;
- Custom start and end time.
Details include Request ID, batch number, retry count, template ID, key event times, and available content snapshots. External images and links are disabled in the content preview, so previewing does not create open or click events.
Message statuses
| Status | Meaning |
|---|---|
| Waiting | The message is queued for downstream processing. |
| Processing | Processing or result confirmation is still in progress. |
| Submitted / Accepted | The sending service or channel accepted the message; this is not final delivery. |
| Delivered | The receiving mail server accepted the message. Inbox placement and reading are not guaranteed. |
| Bounced | A bounce receipt was received; use the safe reason in the details for troubleshooting. |
| Complained | The recipient reported the message as spam; review consent and content. |
| Rejected | Platform policy or the channel rejected the message, such as an unavailable template or all recipients suppressed. |
| Failed | A definite failure occurred during content assembly, channel configuration, authentication, or other processing. |
| Unknown | There is not enough information for a definitive status. |
HTTP 202 applies only to acceptance. An accepted message can later be rejected, fail, or bounce. Do not use HTTP success as a substitute for send records.
Event timeline
The timeline shows recorded key nodes such as processing, submission, channel acceptance, provider receipts, delivery, bounces, rejections, and failures. Open and click show only the first occurrence, not every action.
Open and click events depend on channel tracking support and configuration. Privacy preloading can inflate opens, while blocked remote images can hide genuine opens. Open rate is therefore not an exact reader count.
Failure reasons
Customer details expose a safe fixed vocabulary rather than raw provider text or internal diagnostics:
| Reason | What to check |
|---|---|
invalid_recipient | Address syntax and valid recipients. |
suppressed | Unsubscribe or suppression records; do not retry to bypass suppression. |
template_error | Template review, enabled state, version, and variables. |
rate_limited | Sending rate and the API Key's window or daily quota. |
rejected | Sender identity, template, message type, suppression, and channel rejection. |
send_failed | Keep the Message ID and contact support about content, channel configuration, or authentication. |
delivery_failed | A bounce occurred; review the address, content, domain reputation, and recipient policy. |
complained | Audience consent, unsubscribe handling, and the root cause of complaints. |
marketing_wait_expired | The marketing send's waiting condition expired; contact the platform about the campaign and sending policy. |
unknown | No more specific safe reason is available; give the Message ID to the platform. |
Campaign statuses and statistics
Campaign status is separate from individual message status:
| Campaign status | Meaning |
|---|---|
| Draft | Not submitted for review. |
| Pending review | Submitted and waiting for platform approval. |
| Scheduled | A schedule exists but dispatch has not occurred or approval is still pending. |
| Sending | Dispatch is in progress and cannot be recalled. |
| Dispatch completed | The dispatch workflow ended; not every recipient is necessarily delivered. |
| Cancelled | An unexecuted campaign plan was stopped. |
| Failed | Campaign processing failed; inspect details and recipient rows. |
“Dispatched” counts messages entering the sending flow. Delivered, opened, clicked, and bounced counts come from later outcomes. Refresh statistics, filter recipients, and retry only currently failed recipients from the detail page. A retry acceptance also requires a later result check.
Information to provide when troubleshooting
Provide the Message ID, Request ID/Trace ID, batch number, occurrence time, sender address, and current status. Keep the idempotency key for batch tasks. Never provide the API Secret, complete signature material, or real credentials.
See Event Webhooks for raw event fields, send_failed reason codes, and signature verification.
FAQ
Does delivered mean the message reached the inbox?
No. Delivered means the receiving server accepted it; inbox placement depends on the recipient system.
Related resources
Last updated on