Skip to contentSkip to navigationSkip to topbar
On this page

Update Single Send



API Overview

api-overview page anchor

A Single Send is a one-time, non-automated 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/


PATCH/v3/marketing/singlesends/{id}

Base url: https://api.sendgrid.com (The Twilio SendGrid v3 API)

This endpoint allows you to update a Single Send using a Single Send ID.

You only need to pass the properties you want to update. Any blank or missing properties will remain unaltered.

This endpoint will update a draft of the Single Send but will not send it or schedule it to be sent. Any send_at property value set with this endpoint will prepopulate the Single Send's send date. However, the Single Send will remain an unscheduled draft until it's updated with the Schedule Single Send endpoint or SendGrid application UI.


Authentication

authentication page anchor
Property nameTypeRequiredDescription
authorizationstring
required
Default: Bearer <<YOUR_API_KEY_HERE>>
Property nameTypeRequiredDescription
idstring
required
Encoding type:application/json
Schema
Property nameTypeRequiredDescriptionChild properties
namestring
required

The name of the Single Send.

Min length: 1Max length: 100

categoriesarray[string]
unique

Optional

The categories to associate with this Single Send.

Max items: 10

sendAtstring<date-time> or null

Optional

Set this property to an ISO 8601 formatted date-time when you would like to send the Single Send. Please note that any send_at property value set with this endpoint will prepopulate the send date in the SendGrid user interface (UI). However, the Single Send will remain an unscheduled draft until it's updated with the Schedule Single Send endpoint or SendGrid application UI. Additionally, the now keyword is a valid send_at value only when using the Schedule Single Send endpoint. Setting this property to now with this endpoint will cause an error.


sendToobject

Optional


emailConfigobject

Optional

202400404500
Schema
Property nameTypeRequiredDescriptionChild properties
idstring<uuid>

Optional

The unique ID for the Single Send.


namestring

Optional

The name of the Single Send.

Min length: 1Max length: 100

statusenum<string>

Optional

The current status of the Single Send. The status may be draft, scheduled, or triggered.

Possible values:
draftscheduledtriggered

categoriesarray[string]
unique

Optional

The categories associated with this Single Send.

Max items: 10

sendAtstring<date-time> or null

Optional

An 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.


sendToobject

Optional


updatedAtstring<date-time>

Optional

the ISO 8601 time at which the Single Send was last updated.


createdAtstring<date-time>

Optional

the ISO 8601 time at which the Single Send was created.


emailConfigobject

Optional


warningsarray[object]

Optional

Update Single SendLink to code sample: Update Single Send
1
const client = require("@sendgrid/client");
2
client.setApiKey(process.env.SENDGRID_API_KEY);
3
4
const id = "id";
5
const data = {
6
name: "Miss Christine Morgan",
7
};
8
9
const request = {
10
url: `/v3/marketing/singlesends/${id}`,
11
method: "PATCH",
12
body: data,
13
};
14
15
client
16
.request(request)
17
.then(([response, body]) => {
18
console.log(response.statusCode);
19
console.log(response.body);
20
})
21
.catch((error) => {
22
console.error(error);
23
});