You are viewing the Legacy Marketing Campaigns API reference. For guidance migrating to the current version of Marketing Campaigns, see Migrating from Legacy Marketing Campaigns
For the most up-to-date information on the Sender Identities API, please visit the new Marketing Campaigns Senders API.
To protect your sending reputation and to uphold legitimate sending behavior, Twilio SendGrid requires customers to verify their Sender Identities.
You can verify one or more Sender Identities using either Domain Authentication or Single Sender Verification.
This endpoint allows you to create a new sender identity.
You may create up to 100 unique sender identities.
Bearer <<YOUR_API_KEY_HERE>>
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.
application/json
A nickname for the sender identity. Not used for sending.
The physical address of the sender identity.
Additional sender identity address information.
The city of the sender identity.
The state of the sender identity.
The zipcode of the sender identity.
The country of the sender identity.
A nickname for the sender identity. Not used for sending.
The physical address of the sender identity.
Additional sender identity address information.
The city of the sender identity.
The state of the sender identity.
The zipcode of the sender identity.
The country of the sender identity.
The unique identifier of the sender identity.
If the sender identity is verified or not. Only verified sender identities can be used to send email.
The time the sender identity was last updated.
The time the sender identity was created.
True when the sender id is associated to a campaign in the Draft, Scheduled, or In Progress status. You cannot update or delete a locked sender identity.
1const client = require('@sendgrid/client');2client.setApiKey(process.env.SENDGRID_API_KEY);34const data = {5"nickname": "My Sender ID",6"from": {7"email": "from@example.com",8"name": "Example INC"9},10"reply_to": {11"email": "replyto@example.com",12"name": "Example INC"13},14"address": "123 Elm St.",15"address_2": "Apt. 456",16"city": "Denver",17"state": "Colorado",18"zip": "80202",19"country": "United States"20};2122const request = {23url: `/v3/senders`,24method: 'POST',25body: data26}2728client.request(request)29.then(([response, body]) => {30console.log(response.statusCode);31console.log(response.body);32})33.catch(error => {34console.error(error);35});