A step-by-step plan for moving off Mailjet — replacing the Send API v3.1 call, publishing new DNS records, and the parallel-sending window that keeps your sender reputation intact.
No credit card required · Migration usually takes 1–2 weeks end to end
Code changes
Minutes
Unwrap the Messages array, lowercase the fields, swap the auth
DNS propagation
24–48h
SPF, DKIM and DMARC records need time to settle
Full migration
1–2 wks
Includes the parallel-sending warm-up window
Typical timeline for a mid-size sender. Larger lists or dedicated IP warm-up can take longer.
Sign up free and generate an API key from the dashboard. Keep your Mailjet account active — you'll run both in parallel for a few weeks, not cut over instantly. Note whether you send through the Send API, SMTP relay or Mailjet's campaign tools. Export your contact lists along with your unsubscribed and blocked contacts, so opt-outs move with you.
Add your domain in Sendcorex, then publish the SPF, DKIM and DMARC records it gives you as new DNS entries. Leave Mailjet's SPF include and its mailjet._domainkey DKIM record in place, and merge Sendcorex's SPF include into your existing SPF record rather than adding a second one.
Give it 24–48 hours. Check verification status in the Sendcorex dashboard before sending anything — sending through unverified DNS is what causes the deliverability problems people blame on migrations.
Mailjet's v3.1 payload wraps everything in a Messages array with PascalCase fields (From, To, Subject, HTMLPart) and uses basic auth with an API key and secret key. Sendcorex takes a flat JSON body with a single Bearer token: unwrap the array, lowercase the field names, and rename HTMLPart to html. If you send over SMTP, change the host from in-v3.mailjet.com to smtp.sendcorex.com and use your new API key as both username and password. If you send with TemplateID and Variables, render the template HTML in your own code.
Start with 10–20% of sends routed through Sendcorex, watch delivery and bounce rates in real time, then increase over 1–2 weeks. This lets Sendcorex's IPs warm up against mailbox providers instead of arriving as an unknown sender all at once. If you send in batches, route one batch type through Sendcorex first.
Once 100% of volume runs cleanly through Sendcorex for a few days, remove Mailjet's SPF include and DKIM record, export any contact lists and logs you still need, and cancel the subscription.
await fetch('https://api.mailjet.com/v3.1/send', {
method: 'POST',
headers: {
'Authorization': 'Basic ' + btoa('MJ_API_KEY:MJ_SECRET_KEY'),
'Content-Type': 'application/json',
},
body: JSON.stringify({
Messages: [{
From: { Email: 'hello@yourdomain.com' },
To: [{ Email: 'customer@example.com' }],
Subject: 'Welcome!',
HTMLPart: '<h1>You are in.</h1>',
}],
}),
});const response = await fetch('https://mail.sendcorex.com/v3.0/send', {
method: 'POST',
headers: {
'Authorization': 'YOUR_API_KEY',
'Content-Type': 'application/json',
},
body: JSON.stringify({
to: 'customer@example.com',
from: 'hello@yourdomain.com',
senderName: 'Your Company',
subject: 'Welcome!',
body: '<h1>You are in.</h1>',
}),
});SPF is a single record that includes both Sendcorex and Mailjet for now
DKIM selector for Sendcorex shows as verified in the dashboard
Test send delivered to Gmail, Outlook, and Yahoo test inboxes without landing in spam
Unsubscribed and blocked contacts exported from Mailjet and loaded into Sendcorex
Mailjet event webhooks replaced with a handler for Sendcorex delivery and bounce events
Bounce and complaint rate monitored daily during the ramp-up window
Common questions
Steps and timelines reflect typical migrations as of 2026 and may vary based on list size, DNS provider, and existing authentication setup.
Not if you run a parallel sending window instead of an instant cutover. Sender reputation lives on the sending domain and IP, so warming up Sendcorex's IPs for 1–2 weeks while gradually shifting volume avoids a deliverability dip.
Moving from a different provider?
Ready to move off Mailjet?
Create your account, verify your domain, and start the parallel-sending window today.
No credit card required