When Isaac, Jose, and Tim started SendGrid in 2009, they were motivated to solve a problem that had frustrated them as developers and technical founders at previous startups: Time and time again, they were interrupted from building their core business in order to deal with the complexity of managing email.

They knew there was a way to give this precious time back to developers. They rallied around this idea, and built SendGrid, a pioneer in cloud-based email infrastructure. Fast-forward seven years and SendGrid continues to iterate on this same principle.

Today, we’re happy to announce the public availability our v3/mail/send endpoint. We want our customers to spend more time building their apps and growing their businesses—and less time setting up and managing their email infrastructure.

Why are we so excited about an endpoint?

Our v3/mail/send endpoint ushers in a new era for the SendGrid Web API. The change rounds out last year’s addition of the v3 Web API, making the integration RESTful, and enabling quick and effortless management of email via API.

The new endpoint is the result of months of listening to customer feedback, analyzing support tickets, and reviewing open source issues. In addressing the most common pain points of the v2 API, we’ve greatly improved the developer experience of our most important endpoint.

While v3/mail/send will allow the same functionality as our existing endpoint, the largest addition, called personalizations, will contribute to a significant reduction in developer time. This new addition bundles customizable parameters for a single email into one block. Now, developers simply need to set the default parameters for the send, and then override them with the personalizations they prefer.

Other important improvements and changes within v3/mail/send, include:

  • Intuitive formatting with validation upfront
  • Detailed error reporting to troubleshoot quickly
  • Simplified template parameter requirements
  • Sandbox mode to test the structure and form of an integration before sending an email

Updated Client Libraries

Accompanying v3/mail/send, we’ve delivered updated client libraries for Python, PHP, Go, Java, Node.js, Ruby, and C# that will allow developers to quickly create API calls. To make it even easier for our customers to get started, we’ve included full documentation, code examples, and modern unit testing for v3/mail/send in each library.

Updating these libraries has been a giant endeavor. We’ve documented the effort in order to share our learnings about each language. Along the way, these libraries have been tested and re-tested. The updates will support our customers’ integrations with the SendGrid API, and provide reliability and scalability to their email programs.

What does this mean for users of our v2 mail endpoint?

Today, v3/mail/send becomes our recommended endpoint for all current and future customers.

Our v2 mail endpoint, mail.send.json, will remain in our documentation and will continue to be available as a reliable way to send mail. There will be no interruption to mail sent over the mail.send.json endpoint.

However, we will no longer support v2 endpoints for new features or within our API libraries. Since our future innovation will be focused on v3, we encourage migrating to the new endpoint to take advantage of upcoming features.

Getting Started

We realize that a new endpoint is a big change for many of our customers, so we built a migration guide just for you. When you have the time, we promise that the effort will be worth it.

To learn more and to get started, dive into our v3/mail/send documentation, watch the video overview, and take a look at the V2 vs V3 comparison graphic.



On the Product Marketing team at SendGrid, Cassie is inspired by her frequent conversations with developers and marketers, all of which help to influence the SendGrid product direction as well as how we communicate and deliver our products.