Schedule draft.

POST/api/v1/campaigns/{id}/schedule

Browse API endpoints

Campaigns / CRM REST API

Scope: campaigns:write

Request:

Code example

{ "scheduledAt": 1735689600000 }

scheduledAt is epoch milliseconds, not seconds. A 10-digit seconds value is rejected - otherwise it would parse as a date in 1970 and the campaign would be treated as overdue and sent immediately.

Response:

Code example

{
  "data": {
    "id": "cmp_xyz789",
    "status": "scheduled"
  }
}

The same invalid_status / channel_unsupported / list_required errors apply as with send.

Loading endpoint details...

Build a request

Request example

Documented defaults and example values are ready. Change only the parameters you need.

Connection

Your CRM deployment URL

Replace the Bearer API key placeholder in the copied server-side code. No API key is entered or sent here.

Sub-account ID Agency keys onlyAgency-scoped keys require the X-Sub-Account-Id header.

Path parameters

id Required

Body parameters

scheduledAt Required

Edit the full JSON body

cURL

curl --request POST \
  --url 'https://your-crm.example.com/api/v1/campaigns/ID_HERE/schedule' \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{"scheduledAt":1735689600000}'

This shows a static response from the documentation. It does not send a request to your CRM or use an API key.