Settings - Mail
Mail Settings instruct SendGrid to apply specific settings to every email that you send over SendGrid’s v3 API or SMTP Relay. These settings include how to embed a custom footer, how to manage blocks, spam, and bounces, and more.
For a full list of Twilio SendGrid's Mail Settings, and what each one does, see our Mail Settings documentation.
You can also manage your Mail Settings in the Twilio SendGrid App
Update template mail settings
PATCH /v3/mail_settings/template
Base url: https://api.sendgrid.com
This endpoint allows you to update your current legacy email template settings.
This setting refers to our original email templates. We currently support more fully featured Dynamic Transactional Templates.
The legacy email template setting wraps an HTML template around your email content. This can be useful for sending out marketing email and/or other HTML formatted messages. For instructions on using legacy templates, see how to "Create and Edit Legacy Transactional Templates. For help migrating to our current template system, see "Migrating from Legacy Templates".
Authentication
- API Key
Headers
The on-behalf-of header allows you to make API calls from a parent account on behalf of the parent's Subusers or customer accounts. You will use the parent account's API key when using this header. When making a call on behalf of a customer account, the property value should be "account-id" followed by the customer account's ID (e.g., on-behalf-of: account-id <account-id>). When making a call on behalf of a Subuser, the property value should be the Subuser's username (e.g., on-behalf-of: <subuser-username>). See On Behalf Of for more information.
Request Body
Indicates if you want to enable the legacy email template mail setting.
The new HTML content for your legacy email template.
{
"enabled": true,
"html_content": "<% body %>"
}Responses
Indicates if the legacy email template mail setting is enabled.
The HTML content of your legacy email template.
The ID associated with the error.
The field that generated the error.
The error message.
The ID associated with the error.
The field that generated the error.
The error message.
The ID associated with the error.
The field that generated the error.
The error message.
The ID associated with the error.
The field that generated the error.
The error message.
The ID associated with the error.
The field that generated the error.
The error message.
Need some help?
We all do sometimes. Get help now from the Twilio SendGrid Support Team.
Running into a coding hurdle? Lean on the wisdom of the crowd by browsing the SendGrid tag on Stack Overflow or visiting Twilio's Stack Overflow Collective.
