Suppressions
The suppression list is the memory of who you must not contact. Sending to a suppressed address is refused before it leaves the queue.
List and manage
Suppressions are per channel. GET /email/suppressions and GET /sms/suppressions list them; POST adds an address by hand; DELETE removes one you are sure about. Hard bounces, complaints and unsubscribes add themselves automatically.
cURL
curl -X POST https://api.qsendyx.com/api/v1/email/suppressions \
-H "Authorization: Bearer $QSENDYX_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "address": "user@example.com", "reason": "manual" }'json
{
"data": [
{
"address": "user@example.com",
"reason": "hard_bounce",
"created_at": "2026-07-17T18:05:36Z"
}
],
"next_cursor": null
}Reasons
| Reason | Origin |
|---|---|
| hard_bounce | The recipient server rejected the address permanently. |
| complaint | The recipient marked a message as spam. |
| unsubscribe | The recipient opted out. |
| manual | You added the address yourself. |
Removing a suppression does not undo the reason it was added. Delete a hard-bounce entry only if you know the address is now valid — sending to dead addresses is what wrecks a sender reputation, and reputation does not roll back.