Submit over SMTP without losing operational context.
Create SMTP username/password credentials in SendAxion and use SMTP AUTH on submission ports 587 or 465. Credentials can be transactional, marketing, or both.
Built as part of one sending operation.
SMTP AUTH credentials
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Ports 587 and 465
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Transactional stream
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Marketing stream
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Optional both-stream credential
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Activity retained in SendAxion
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>"
}'