- What is the v3 Mail Send endpoint?
- Do I have to have a certain type of account to use the v3 Mail Send endpoint?
- I’m currently using the v2 Mail Send endpoint. Should I switch to v3?
- How do I migrate from V2 to V3?
- What’s the difference between sending mail via SMTP and the Web API?
- Can I send marketing email over the v3 Mail Send endpoint?
- Are there limits on how often I can send email and how many recipients I can send to?
- Why did you remove the x-smtpapi parameter? Can I still change my mail settings, tracking settings, and unique arguments?
- Where can I find more information about the v3 Mail Send endpoint?
The v3 Mail Send endpoint is the latest version of SendGrid’s Web API endpoint that allows you to send email by making a simple HTTP request. The introduction of the v3 Mail Send endpoint signifies the completion of our RESTful Web API v3.
The v3 Mail Send endpoint is available on all SendGrid pricing plans. The same plan based limitations on the volume of email you may send still apply to the v3 Mail Send endpoint. For more information, please visit our Pricing Page.
The v3 Mail Send endpoint offers many improvements over the v2 endpoint, and we highly encourage all users to migrate their email programs from the v2 to the v3 endpoint. While you may not notice any significant changes in the functionality offered by the v3 mail send endpoint, you will find it to be significantly easier to use. The v3 Mail Send endpoint offers a more comprehensive and consistent JSON schema, intuitive validation with more in depth error messages, and complete coverage across all 7 of our supported libraries.
If you are currently using the v2 Mail Send endpoint, we have provided some helpful instructions on how to migrate from sending mail over the Web API v2 to the Web API v3.
Sending email via the SMTP-Relay is a quick and simple way to integrate your existing SMTP code with SendGrid’s email functionality. All you have to do is modify your SMTP configuration to point to SendGrid’s SMTP server and your email will be routed through SendGrid’s SMTP-Relay. You may then specify special instructions for how you would like SendGrid to handle your email by means of the X-SMTPAPI header.
The Web API, on the other hand, requires you to make an HTTP request to an endpoint in SendGrid’s API. Previously, SendGrid has only offered a mail sending endpoint in the Web API v2, but now you can use the RESTful Web API v3 to send your email. Simply make an
HTTP POST request to
https://api.sendgrid.com/v3/mail/send/beta with the data for your email included in a JSON payload. For more information, please visit our v3 Mail Send documentation.
You can send any type of email (transactional or marketing) over the v3 Mail Send endpoint. However, we recommend you take a look at our Marketing Campaigns API for a more robust marketing feature set (including segmentation and templates).
There are rate limits on how frequently you can call the v3 Mail Send endpoint. Currently, you may make up to 3,000 requests per second to our endpoint. Each email you send may include up to 1000 recipients. For more information on other limitations, and how this may impact your integration, please visit our v3 Mail Send overview.
Why did you remove the x-smtpapi parameter? Can I still change my mail settings, tracking settings, and unique arguments?
Everything that could be accomplished by using the x-smtpapi parameter in the v2 Mail Send endpoint can still be done with the v3 endpoint. While the v2 Mail Send endpoint required you to include a separate block of JSON for various mail settings within the single x-smtpapi parameter, the v3 endpoint payload structure includes each setting as a separate parameter. This allows for a quicker and more consistent integration and helps with validation and debugging.
For more general information about the v3 Mail Send endpoint, please visit the v3 Mail Send Overview. Below, you will find links to more in depth information about the endpoint.