Trigger a one-time send
Changed onTrigger a one-time send (referred to as a "newsletter" in our APIs) immediately. It must be in a draft state. If it has already been sent, you'll get a 400 error. The recipients are fixed when you create the one-time send. If you're not sure who will receive it, you can use the List one-time sends endpoint to get a list of one-time sends and their recipients.
To reschedule a one-time send, use the Schedule a one-time send endpoint instead.
Request
- Base URLhttps://api.customer.io
- URLhttps://api.customer.io/v1/newsletters/{newsletter_id}/send
- AuthHTTP bearer
Request body
Example request
{
"rate_limit_email_rate": 500,
"rate_limit_time_period": 60,
"rate_limit_spread": true
}Response
The one-time send is queued.
Example response
{
"newsletter": {
"id": 128275,
"deduplicate_id": "128275:1481653929",
"type": "email",
"content_ids": [
45
],
"name": "Weekly Product Update",
"sent_at": 1481653929,
"send_state": "sent",
"scheduled_at": null,
"created": 1481653919,
"updated": 1481653929,
"recipient_segment_ids": [
42,
99
],
"tags": [
"Product Updates"
],
"subscription_topic_id": 5
}
}Changes
- breaking
the response property
/became nullable for the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status
- breaking
- breaking
added
subschema #2to the request bodyallOflist - breaking
the request's body type changed from
objectto no type - warning
removed the request property
- warning
removed the request property
- warning
removed the request property
- info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status
- breaking