Appearance
Email
Send transactional emails through Sendivent. You'll need to verify your sending domain first.
INFO
Your email integration is shared between sandbox and production — set it up once, use it everywhere.
Domain setup
Configure DNS so mailbox providers can authenticate your messages. Without verification, email sending will fail.
Step 1: Add your domain
- Go to Channels → Email in your dashboard
- Click Add domain
- Enter your domain (e.g.
yourdomain.com)
Step 2: Add DNS records
After adding your domain, the dashboard shows the exact DNS records to add. Copy them to your DNS provider.
Where to find your records
Go to Channels → Email in your dashboard — your domain's specific DKIM, SPF, and DMARC values are displayed there.
| Record | Required | Purpose |
|---|---|---|
| DKIM | Yes | Proves emails are authentically from you |
| SPF | Yes | Authorizes Sendivent to send on your behalf |
| DMARC | Recommended | Tells receivers what to do with failed checks |
Already have an SPF record?
Don't create a second one — you can only have one SPF record per domain. Add the provided include: before the final ~all or -all.
TIP
DNS record formats differ between registrars. If verification fails, double-check the host/name field formatting in your DNS UI.
Step 3: Verify
- Return to Channels → Email
- Click Verify next to your domain
DNS changes can take time to propagate depending on your DNS provider.
Email overrides
Example request body using overrides.email:
json
{
"to": "user@example.com",
"overrides": {
"email": {
"subject": "Your Invoice #123",
"reply_to": "billing@company.com",
"cc": ["accounts@company.com"],
"bcc": ["audit@company.com"]
}
}
}| Field | Type | Description |
|---|---|---|
subject | string | Override the subject line |
reply_to | string | string[] | Reply-to address(es) |
cc | string | string[] | CC recipients |
bcc | string | string[] | BCC recipients |
Custom Sender
Send from any email address on your verified domain. Use for personalized communication — support agents, sales reps, account managers.
bash
curl -X POST "https://api.sendivent.com/v1/send/welcome" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "customer@example.com",
"from": "sarah@yourdomain.com",
"payload": { "rep_name": "Sarah" }
}'Domain verification required
Your sending domain must be verified (see Domain setup). Once verified, any email address from that domain can be used — no per-address registration needed.
Difference from SMS: SMS requires each phone number to be individually verified. Email uses domain-level verification, so sales@, support@, john@ etc. all work once the domain is verified.
Troubleshooting
Email not received
- Check spam/junk folder (especially for new senders)
- Confirm domain is verified (DKIM/SPF/DMARC)
- Check delivery status in Activity
Bounces and complaints
Sendivent automatically protects your sender reputation — no action needed from you.
| Type | Sendivent action |
|---|---|
| Hard bounce | Suppresses address — future sends blocked |
| Soft bounce | Monitors — suppresses after 3 bounces in 7 days |
| Complaint | Suppresses immediately — user marked as spam |
Suppressed addresses are automatically excluded from future sends.
See also
- Routing — Force email vs auto-routing
- Deliveries — Statuses and failure reasons
- Templates — Dynamic content