Recurring schedules

A cadence generates slots, not content. Fill them with schedule_batch.

A cadence is a standing pattern — every Monday, Wednesday and Friday at 09:00 New York time — instead of scheduling one post at a time.

A recurrence schedules SLOTS, not content. create_recurrence does not write posts and never invents any. The pattern is: create the cadence, then fill its slots with schedule_batch.

create_recurrence

Parameter	Type	Notes
site	string	Site handle or URL. Required.
days_of_week	number[]	0 = Sunday through 6 = Saturday. Required. [1,3,5] is Monday, Wednesday, Friday.
time_of_day	"HH:MM"	24-hour local time in the timezone below, e.g. "09:00". Required.
timezone	IANA timezone	REQUIRED — e.g. "America/New_York". There is no default and no guess.
ends_on	YYYY-MM-DD	Optional. Without it the cadence runs until you cancel it.

create_recurrence({
  site: "myblog",
  days_of_week: [1, 3, 5],
  time_of_day: "09:00",
  timezone: "America/New_York",
  ends_on: "2026-12-31"
})

The fields are flat — days_of_week, time_of_day, timezone, ends_on — not a nested rule object. days_of_week uses 0 for Sunday through 6 for Saturday.

timezone is required

time_of_day is a wall-clock time, which is meaningless on its own. timezone is therefore required and must be an IANA name such as "Europe/London". A cadence without one is rejected, not guessed — Pressbotics will not pick a timezone and publish your week at the wrong hour.

Listing and cancelling

list_recurrences returns each cadence with its id, pattern, timezone, end date and whether it is active.
cancel_recurrence stops future slots being generated. Slots already scheduled remain and must be cancelled individually with cancel_scheduled.

How slots behave

Slots are generated ahead of time, roughly three months out, and topped up as time passes.
Each slot is an ordinary scheduled post. Move one with reschedule_post, cancel one with cancel_scheduled, without disturbing the rest.
Every instance goes through the same approval policy as any other post.
A cadence stops generating once the account is paused or the site is removed.

What can go wrong

Expecting content to appear. A cadence creates slots; schedule_batch puts posts in them.
Sending a nested rule object. The agent-facing fields are flat.
Omitting timezone. The call is refused.
Approvals piling up on a review-all site. A daily cadence means a daily approval.
Changing a site's time zone after the cadence was created. Existing slots keep their stored instant.