Attach sending identity before traffic leaves the platform.
Sending domains track verification state, SPF, DKIM, DMARC, DNS publication method, stream type, and the required records needed before API sending is accepted.
Built as part of one sending operation.
Domain preflight checks
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Manual or Cloudflare-assisted DNS publication
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
DKIM key generation
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
SPF/DKIM/DMARC status
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Transactional, marketing or both stream type
Kept close to the rest of SendAxion so operators can follow the signal without jumping between disconnected systems.
Re-verification endpoint
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>"
}'