Stop known-bad recipients from becoming repeated sends.
SendAxion checks suppressions before API delivery and can automatically suppress recipients after hard-bounce or complaint signals while avoiding suppression for selected transient or policy categories.
Built as part of one sending operation.
Pre-send recipient checks
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Hard-bounce suppression
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Complaint suppression
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Message-level source event linkage
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Account-scoped suppression list
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
See the message layer in context.
The examples below use only endpoint names, key formats, event types, and submission behavior verified in the current SendAxion codebase.
curl -X POST https://dashboard.sendaxion.com/api/v1/messages \
-H "Authorization: Bearer pp_live_••••••" \
-H "Content-Type: application/json" \
-d '{
"from": "alerts@yourdomain.com",
"to": ["customer@example.com"],
"subject": "Security alert",
"html": "<strong>New sign-in detected</strong>"
}'