Understand the vocabulary of a SendAxion message journey.
The current event model covers reception, delivery, transient failure, bounce, feedback, expiration, administrative bounce, rejection, and out-of-band outcomes.
Built as part of one sending operation.
reception
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
delivery
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
transient_failure
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
bounce
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
feedback
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
expiration
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
admin_bounce
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
rejection
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
out_of_band
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>"
}'