Campaigns

Update campaign schedule

Updates the sending schedule for a campaign including timezone, days, time windows, and frequency. daysSchedule is sent as an array of days, but the response returns it as one comma-separated string of weekday numbers, such as "1,2,3,4,5". GET /campaigns/{id} returns it the same way.

put/campaigns/{id}/schedule

Request

  • Base URL: https://api.emailchaser.com/r
  • URL: https://api.emailchaser.com/r/campaigns/{id}/schedule
  • Auth: HTTP bearer

Path parameters

idinteger required

Campaign ID

Request body

daysSchedulestring[]

DaysSchedule is the set of weekdays the campaign may send on. Accepts weekday numbers as strings, where Sunday is 0 ("1" is Monday), or weekday names such as "monday". Names are matched case-insensitively and common short forms ("mon", "tues") work. It is sent as an array, but stored as numbers and returned as one comma-separated string: a request sending Monday to Friday by name reads back as "1,2,3,4,5".

For multiple leads scheduled campaigns (flow 3) and API campaigns.

endSchedulestring
everyScheduleinteger
maximumTimeBetweenEmailsinteger
minimumTimeBetweenEmailsinteger
sendAtstring

For single lead scheduled campaigns (flow 2)

startSchedulestring
timezonestring required

Common field for all flows

Example request

{
  "daysSchedule": [
    "1",
    "2",
    "3",
    "4",
    "5"
  ]
}

Response

Campaign schedule updated successfully

messagestring

Example response

{
  "campaign": {
    "daysSchedule": "1,2,3,4,5",
    "endSchedule": "17:00",
    "everySchedule": 30,
    "id": 123,
    "maximumTimeBetweenEmails": 15,
    "minimumTimeBetweenEmails": 5,
    "name": "Q1 Outreach Campaign",
    "startSchedule": "09:00",
    "timezone": "America/New_York"
  },
  "message": "campaign schedule updated successfully"
}

Changes

No recorded changes to this operation across all 1 revision of this API.