Send through the message API and keep the resulting message traceable.
The live SendAxion message endpoint is POST /api/v1/messages on the dashboard service. It authenticates with a pp_live_ bearer key and requires a verified sending domain.
Built as part of one sending operation.
POST /api/v1/messages
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Bearer pp_live_ API keys
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
from, to, subject required
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
text and/or html body
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
reply_to and custom headers
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
campaign identifiers
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
202 response with message_id
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>"
}'