Single Sends
A Single Send is a one-time nonautomated email message delivered to a list or segment of your audience. A Single Send may be sent immediately or scheduled for future delivery.
Single Sends can serve many use cases, including promotional offers, engagement campaigns, newsletters, announcements, legal notices, or policy updates.
The Single Sends API allows you to create, retrieve, update, delete, schedule, and deliver your Single Sends. There are also endpoints for searching and statistics to help you maintain and alter your Single Sends as you learn more and further develop your campaigns.
The Single Sends API changed on May 6, 2020. Please check the SendGrid Knowledge Center for updates and instructions here: https://sendgrid.com/docs/for-developers/sending-email/single-sends-2020-update/
Get Single Send by ID
GET /v3/marketing/singlesends/{id}
Base url: https://api.sendgrid.com
This endpoint allows you to retrieve details about one Single Send using a Single Send ID.
You can retrieve all of your Single Sends by making a GET request to the /marketing/singlesends endpoint.
Authentication
- API Key
Headers
Path Parameters
The ID of the Event Webhook you want to retrieve.
default: NoneResponses
The unique ID for the Single Send.
format: uuidThe name of the Single Send.
maxLength: 100minLength: 1The current status of the Single Send. The status may be draft, scheduled, or triggered.
The categories associated with this Single Send.
maxItems: 10uniqueItems: TrueAn ISO 8601 formatted date-time when the Single Send is set to be sent. Please note that any send_at property value will have no effect while the Single Send status is draft. You must update the Single Send with the Schedule Single Send endpoint or SendGrid application UI to schedule it.
The IDs of each contact list to which the Single Send will be sent.
maxItems: 50The IDs of each segment to which the Single Send will be sent.
maxItems: 10If this property is set to true, the Single Send will be sent to all of your contacts. If it's set to false, at least one list_ids or segment_ids value must be provided before the Single Send is scheduled to be sent.
the ISO 8601 time at which the Single Send was last updated.
format: date-timethe ISO 8601 time at which the Single Send was created.
format: date-timeThe subject line of the Single Send. This property is not used when a design_id value is set.
The HTML content of the Single Send. This property is not used when a design_id value is set.
The plain text content of the Single Send. This property is not used when a design_id value is set.
If this property is set to true, plain_content is always generated from html_content. If it's set to false, plain_content is not altered.
A design_id can be used in place of html_content, plain_content, and/or subject. You can retrieve a design's ID from the List Designs endpoint or by pulling it from the design's detail page URL in the Marketing Campaigns App.
The editor, design or code, used to modify the Single Send's design in the Marketing Campaigns application user interface.
The ID of the Suppression Group to allow recipients to unsubscribe. You must provide a suppression_group_id or the custom_unsubscribe_url with your Single Send.
The URL allowing recipients to unsubscribe. You must provide a custom_unsubscribe_url or a suppression_group_id with your Single Send.
The ID of the verified sender from whom the Single Send will be sent. You can retrieve a verified sender's ID from the Get Verified Senders endpoint or by pulling it from the sender's detail page URL in the SendGrid App.
The name of the IP Pool from which the Single Send emails are sent.
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.
