Bounces & Complaints
Know which emails did not make it, and why
Hard and soft bounces, blocks, spam complaints and abuse reports in one feed. Poll it with a cursor, clean your lists and never miss an event.
- JSON commands
- Cursor polling
- Up to 1000 per call
- Last 90 days
- Read-only
https://g.sendcorex.com/v1/feedbackfeedback:readHow it works
Everything that came back
Bounces at send time, bounce messages that arrive later, feedback loops from Microsoft and Yahoo, and the abuse reports people send us. One feed, one shape.
Hard, soft or blocked
Not every 5xx is a bad address. Each event says if the address is gone (hard), if it was temporary (soft), or if the message itself was refused (blocked).
Built for polling
Oldest first with a cursor that always comes back. Save it, send it again, and you get exactly what is new. One event per email, never twice.
Get started
Only the key is needed before your first request.
- 1
Create an API key with feedback:read
In the dashboard, open Developers → API Keys and create a key with the feedback:read scope, or add it to a key you already use.
The webmail token does not work here. This API uses the dashboard API key.
- 2
Poll the feed
List Feedback returns what is new since your cursor. Keep the next_cursor it gives you and send it on the next call.
- 3
Look up one email
Get Email tells you everything that came back for one email id: its bounce, its complaint, or why it was not sent.
The event
Both commands return events in this shape.
{
"email_id": "9b7e4c21-0d3a-4e8f-a6b1-5c2d7e9f1a30",
"kind": "bounce_hard",
"source": "smtp",
"recipient": "old.address@gmail.com",
"from": "noreply@yourdomain.com",
"smtp_code": 550,
"enhanced_code": "5.1.1",
"diagnostic": "550-5.1.1 The email account that you tried to reach does not exist.",
"at": "2026-10-17T05:58:44.031Z"
}kindbounce_hard, bounce_soft, blocked, complaint or dropped. Only hard bounces and complaints mean "stop sending to this address".
sourceWhere it came from: the SMTP answer, a later bounce message, a feedback loop or an abuse report.
smtp_code / enhanced_codeThe code the server answered, like 550 and 5.1.1. diagnostic has the full text.
email_idThe same id as in Logs and in the webhooks, so you can join them.
Your first request
Your hard bounces and complaints since the start of the month. Replace SENDCOREX_API_KEY with your API key.
curl -X POST 'https://g.sendcorex.com/v1/feedback' \
-H "Authorization: $SENDCOREX_API_KEY" \
-H 'Content-Type: application/json' \
-d '{
"commands": [
{ "command": "list_feedback", "args": { "since": "2026-10-01T00:00:00Z", "kinds": ["bounce_hard", "complaint"] } }
]
}'You get the events oldest first and a next_cursor. Save it and send it on the next call to get only what is new. The same request in 8 languages is in List Feedback.
Common tasks
Keep your lists clean
Poll every 30 seconds and remove addresses that hard bounce or complain. Your reputation stays high and your sends stay out of spam.
PollingCatch complaints fast
Filter the feed to complaint and alert your team: a spike in complaints is the first sign a campaign is going wrong.
Filtering by kindExplain a missing email
Given an email id, show your customer the exact reason the receiving server gave.
Get EmailGet them pushed instead
The bounced and fbl_complaint webhooks send the same events the moment they happen. Use polling as the safety net.
WebhooksFull reference
Everything marked CMD is a command sent through POST /v1/feedback, up to 20 per request.