Marketing Campaigns
If you use SendGrid Marketing Campaigns, plan that move to Sendix Audience and Broadcasts separately from transactional mail.
Keep your app logic and templates. Swap the SMTP credential or the Mail Send call, recreate Event Webhook subscriptions, carry over suppression lists and move traffic at your own pace.
- SMTP_HOST=smtp.sendgrid.net+ SMTP_HOST=smtp.sendix.dev- SMTP_PORT=587+ SMTP_PORT=587 # STARTTLS- SMTP_USER=apikey+ SMTP_USER=<username from dashboard>- SMTP_PASS=SG.••••••••+ SMTP_PASS=<Sendix API key>Verify your domain in Sendix (DKIM, bounce CNAME and include:mail.sendix.dev in SPF). Then either change SMTP from smtp.sendgrid.net with the "apikey" user to smtp.sendix.dev:587 with a Sendix API key, or replace calls to /v3/mail/send with POST https://sendix.dev/api/v1/emails. Map Event Webhook events (delivered → email.delivered, bounce → email.bounced, spamreport → email.complained) and import your bounce, unsubscribe and spam-report lists as Sendix suppressions.
Run SendGrid and Sendix side by side until the new path is proven.
Publish the Sendix DKIM TXT record (<selector>._domainkey), the bounce CNAME (bounce.<your-domain> → bounce.sendix.dev) and add include:mail.sendix.dev to your SPF record. SendGrid’s DKIM records can stay while both providers send.
SMTP users change host, username and password — the "apikey" login becomes your Sendix username with an API key as password. API users replace the personalizations payload with from, to, subject and html/text, or template_id with template_data.
Create a Sendix webhook for the events you consumed from SendGrid, verify X-Sendix-Signature, and map event names with the table below.
Export bounced, unsubscribed and complained addresses from SendGrid, add them with POST /v1/suppressions, move traffic gradually, then remove SendGrid’s SPF include.
Where each piece of your current integration lives in Sendix.
| Concept | SendGrid | Sendix |
|---|---|---|
| SMTP server | SendGridsmtp.sendgrid.net:587 | Sendixsmtp.sendix.dev:587 (STARTTLS) |
| SMTP login | SendGridUsername "apikey", API key as password | SendixUsername from your dashboard, API key as password |
| Send endpoint | SendGridPOST https://api.sendgrid.com/v3/mail/send | SendixPOST https://sendix.dev/api/v1/emails (JSON) |
| API authentication | SendGridAuthorization: Bearer <API key> | SendixAuthorization: Bearer <API key> |
| Templates | SendGridDynamic templates (Handlebars) | SendixVersioned {{variable}} templates (template_id + template_data) |
| Delivered event | SendGriddelivered | Sendixemail.delivered |
| Bounce event | SendGridbounce (dropped when suppressed) | Sendixemail.bounced |
| Complaint event | SendGridspamreport | Sendixemail.complained |
| Webhook security | SendGridSigned Event Webhook (ECDSA) | SendixX-Sendix-Signature (HMAC-SHA256) |
| Suppressions | SendGridBounces, blocks, spam reports, invalid emails, unsubscribes | SendixSuppression list API (/v1/suppressions) |
SendGrid is a trademark of its owner. Its column summarizes public documentation as of September 12, 2026; confirm current details in SendGrid’s docs before migrating.
SendGrid features that need a plan, and where they land in Sendix.
If you use SendGrid Marketing Campaigns, plan that move to Sendix Audience and Broadcasts separately from transactional mail.
Handlebars-style {{variables}} usually carry over. Recreate each template in Sendix, preview it with test data and publish a version before switching.
SendGrid unsubscribe groups map most closely to Sendix topics, which let contacts choose the kinds of mail they receive.
Compare your monthly and daily volume with the limits on the Sendix pricing page before the cut-over.
Answers for teams moving from SendGrid.
No. Sendix uses its own JSON body (from, to, subject, html, text, template_id, template_data, tags), so API integrations need a small change. SMTP integrations only need new credentials.
Yes. Each provider signs with its own DKIM selector, and a single SPF record can include both during the transition — keep it to one SPF record and within the 10-DNS-lookup limit. A domain can have only one DMARC record, so keep your existing one if it already has a policy.
The Node SDK and CLI exist as source packages but are not yet published to npm, so most teams integrate over the REST API (plain HTTPS and JSON) or SMTP. Neither needs an extra dependency.
Import them as suppressions with POST /v1/suppressions and a reason of hard_bounce, unsubscribed or complained. Sendix then reports email.suppressed instead of sending to those addresses.
The free plan includes 1,000 emails per month. Paid plans change volume and limits, not your API calls or SMTP settings.
1,000 emails free every month. No credit card required. Upgrade only when you outgrow the free tier — and we will let you know when that time comes.
Managed SaaS platform · Native SMTP engine · SOC 2 in progress