Send Emails | Twilio

This operation creates and sends out emails to the specified recipients.

Authentication

AuthorizationBasic

Basic authentication of the form Basic <account_id:auth_token>.

AuthorizationBasic

Basic authentication of the form Basic <api_key:api_key_secret>.

Request

This endpoint expects an object.

fromobjectRequired

The sending identity to associate with the Email.

Use EmailAddressSender to directly specify the email address that the Email will appear to come ‘from’.

The sending identity to associate with the `Email`. - Use `EmailAddressSender` to directly specify the email address that the Email will appear to come 'from'.

tolist of objectsRequired

A list of recipients to send the email(s) to.

contentobjectRequired

The content of the Email.

Use EmailContent to supply a text/html email body. Optionally provide a plain/text body for clients that do not support HTML. If none is specified, Twilio will auto-create one from your HTML email body.

Use the Liquid templating language for personalization in any text-based field.
When using a templated content, use the variables field on each recipient to specify the values to substitute.
For each variable you specify in your template, you should have a matching key in each recipient’s variables object.
When targeting Profile recipients, you may specify variables with values that reference stored fields, on the Profile — for example: ${Twilio.Profile.dateLastPurchase} ${Twilio.Profile.firstName} or ${Twilio.Profile.myCustomField}.

The content of the Email. - Use `EmailContent` to supply a `text/html` email body. Optionally provide a `plain/text` body for clients that do not support HTML. If none is specified, Twilio will auto-create one from your HTML email body. *** * Use the [Liquid](https://shopify.github.io/liquid/) templating language for personalization in any text-based field. * When using a templated content, use the `variables` field on each recipient to specify the values to substitute. * For each variable you specify in your template, you should have a matching key in each recipient's `variables` object. * When targeting `Profile` recipients, you may specify `variables` with values that reference stored fields, on the `Profile` -- for example: `${Twilio.Profile.dateLastPurchase}` `${Twilio.Profile.firstName}` or `${Twilio.Profile.myCustomField}`.

tagsmap from strings to stringsOptional

Custom metadata in the form of key-value pairs. Maximum size of a tag key is 128 characters. Maximum size of a tag value is 256 characters. There can be a maximum of 10 key-value pairs.

This field can be templated with Liquid. Specify variables with each recipient for personalization.

Custom metadata in the form of key-value pairs. Maximum size of a tag key is 128 characters. Maximum size of a tag value is 256 characters. There can be a maximum of 10 key-value pairs. This field can be templated with [Liquid](https://shopify.github.io/liquid/). Specify `variables` with each recipient for personalization.

scheduleobjectOptional

A schedule defines when a communication will be sent to a recipient.

ipPoolNamestringOptional2-64 characters

The name of the IP Pool to use for sending Emails.

If not specified, all dedicated IPs associated with your account will be considered for sending.

IP pools are only available to accounts with dedicated IPs.

This field can be templated with Liquid. Specify variables with each recipient for personalization.

The name of the IP Pool to use for sending Emails. If not specified, all dedicated IPs associated with your account will be considered for sending. IP pools are only available to accounts with dedicated IPs. This field can be templated with [Liquid](https://shopify.github.io/liquid/). Specify `variables` with each recipient for personalization.

Response headers

Locationstring or null

The location (uri) of the Operation resource. Issue a GET request to this URI to retrieve the status of the Operation.

Response

The request was accepted and an Operation was created to track its progress. The response body contains the ID and link to the Operation resource.

operationIdstringformat: "^comms_operation_[0-7][a-hjkmnpqrstv-z0-9]{25,34}"

The Operation ID is an identifier that can be used to correlate all of the resources created in a request. Issue a GET request to the resource list location, using the Operation ID as a query parameter to retrieve the resources that correlate with the Operation.

operationLocationstringformat: "uri"

The location (uri) of the Operation resource identified by operationId.

Errors

The content of the Email.

Use EmailContent to supply a text/html email body. Optionally provide a plain/text body for clients that do not support HTML. If none is specified, Twilio will auto-create one from your HTML email body.

Use the Liquid templating language for personalization in any text-based field.
When using a templated content, use the variables field on each recipient to specify the values to substitute.
For each variable you specify in your template, you should have a matching key in each recipient’s variables object.
When targeting Profile recipients, you may specify variables with values that reference stored fields, on the Profile — for example: ${Twilio.Profile.dateLastPurchase} ${Twilio.Profile.firstName} or ${Twilio.Profile.myCustomField}.

1	curl -X POST https://comms.twilio.com/v1/Emails \
2	-H "Content-Type: application/json" \
3	-u "<accountId>:<authToken>" \
4	-d '{
5	"from": {
6	"address": "support@example.company.io",
7	"name": "Cool Co Support"
8	},
9	"to": [
10	{
11	"address": "bob@example.com",
12	"name": "Bob Smith"
13	}
14	],
15	"content": {
16	"html": "<html><body>Hey, <br/><br/>Cake</b></body></html>",
17	"text": "Hey, the cake is ready.",
18	"subject": "Re: Wedding Cake",
19	"attachments": []
20	}
21	}'

1	{
2	"operationId": "comms_operation_01h9krwprkeee8fzqspvwy6nq8",
3	"operationLocation": "https://comms.twilio.com/v1/Emails/Operations/comms_operation_01h9krwprkeee8fzqspvwy6nq8"
4	}