We gave you a sneak peek a couple of months ago, but now we’re finally here. The time has come to say goodbye to our beloved Send API version 3, and unveil our most improved version, v3.1!
Over the past three years, our Send API has been doing a great job at routing all your transactional emails, and thanks to your valuable feedback, we’re now ready to introduce its latest version, which is here to make your sending experience even better.
Ladies and gentlemen, after months of hard work and many valuable lessons learned from our developers community during its beta, Send API 3.1 is ready to become our official and stable version. Cue applause.
Don’t worry, we’ll continue to support Send API 3.0, but we’re sure you’re going to love v3.1!
So, why did we decide it was time for a new version?
Let’s be honest, no matter how much we enjoy finding hacks and workarounds, there’s not a developer out there that wouldn’t prefer a pain-free experience while at work. And yes, we know how painful API calls can get, especially when you combine little to no documentation with erratic behaviors, obscure input, response payloads…
So, to make your life easier and your work more manageable, we decided to focus on providing our users with a seamless Send API onboarding journey. We provide you with a complete documentation made by developers for developers, and meaningful payloads to offer a smooth experience.
And to make this new version even more advanced, with a real focus on performance and scalability, we decided to rebuild it entirely from scratch, moving away from our previous code in Free Pascal and opting for a new tech stack based on Golang, Cassandra and Kafka, to name a few. Sounds good, right?
Awesome! Show me the code, please?
The first thing you’ll notice is how much the onboarding user experience has improved in this new version. Want to see it in action? Check them out here:
Sending messages
Whether you’re sending one or more messages, it will be as simple as making a single HTTP call on the /v3.1/send endpoint. Send API will accept a JSON payload with a single Messages array property containing up to 100 messages. Clear and easy, isn’t it?
New detailed error and success payloads
Thanks to the feedback we received from our community, we decided it was time for a drastic improvement on our response payloads. We now perform strict checks on all your input payload, which means you’ll receive synchronous feedback about what went wrong, in order to cut down your debugging time. On our side, this also means a reduced number of malformed emails entering our system. Check out this example of an error payload.
Something worth noting is that these errors are generated for each message independently, and only the sending process of the failing messages will be blocked.
Our success reporting is also more detailed than it used to be. Success payloads provide, for instance, a MessageHref property, a URL that points to the API endpoint on which to retrieve the message metadata. Tracking your emails straight from the sending has never been easier.
Both success and error payloads are now sent together, in the same order followed by the input payload messages, to make checking the fail or pass status of your messages much easier.
URL Tagging
Sending emails fast, at scale is one side of the business, but being able to monitor how much they perform is critical. Our mission is to offer you all the tools you need to be able to achieve this. Thanks to Send API v3.1, you can now provide us with the proper tracking markers and we’ll make sure all the links your emails contain are properly tagged and report back to you.
Sandbox mode
Sending emails for development purposes comes with a cost (yeah, they still count towards your plan’s email quota), and you’re never fully protected from delivering undesired emails to your customers. Whether you’re experimenting with the API for the first time or just checking your code, there might be times when you’d like to test an email payload without having to send a real email.
To make your life easier as a developer, we’ve incorporated a brand new sandbox mode. In your input payload, set SandboxMode to true. This will tell the Send API to process your messages as if you wanted to send them, without actually sending them, so you can properly test and troubleshoot your message easily!
You can find the full list of mandatory and optional properties for each message here.
Try It Live!
If you’ve been using Mailjet’s API, you know how much we value good documentation. We know that no user experience would be good enough without a complete documentation to enable developers to implement our new Send API 3.1 to its full potential. That’s why this new version comes with a library of detailed API guides, fully up-to-date Passport code snippets and support in all our wrappers for you that will allow you to truly master it and make the most of it!
Finally, it’s all thanks to you!
Yeah, we wouldn’t be able to share the greatness that is our Send API 3.1 with you all if it wasn’t for the valuable help from our awesome developer community. You answered our call when we opened its beta and exceeded our expectations in terms of engagement and feedback.
And so, it is thanks to our community that we have been able to offer a final product that is much more advanced than its original version, with significant improvements in areas such as error reportings. Kudos to you all!
Can’t wait to try out our new Send API 3.1? Jump over to the documentation and get started with it today! We’re sure you’ll love it just as much as we do.
You’re an active user of Send API 3.0? Even if we do encourage you to switch to 3.1 to benefit from all the new features, we’ll keep supporting the 3.0 as long as needed, so you’ve got nothing to worry about. You’ll find the migration documentation here and should you need to check something about v3, it’s still documented here too.
Learn how Mailjet can improve your developer experience by checking out Mailjet for Developers, and subscribing to our dev-only newsletter to be the first to hear about all our news. Want to join us for a chat? Tweet us at @mailjetdev!