Update Recurring Post
Update the next run, content, or cadence of a recurring series.
Update the next run, content, or cadence of a recurring series.
/api/v1/recurring-post/{recurringPostId}Update an active or paused recurring series.
startsAt is required because editing a series replaces its scheduled posts from that occurrence onward. Other fields are optional.
{
"startsAt": "2026-10-02T10:00:00Z",
"text": "Updated weekly copy",
"recurrence": {
"interval": 2,
"endType": "AFTER_OCCURRENCES",
"occurrenceCount": 10
}
}{
"startsAt": "2026-10-02T10:00:00Z",
"text": "Updated weekly copy",
"recurrence": {
"interval": 2,
"endType": "AFTER_OCCURRENCES",
"occurrenceCount": 10
}
}| Field | Type | Required | Description |
|---|---|---|---|
startsAt | string | Yes | New next occurrence, at least two minutes in the future. |
text | string | No | Replacement text for future occurrences. |
media | string[] | object[] | No | Replacement media for future occurrences. |
recurrence | object | No | Partial recurrence fields. Omitted values keep their current setting. |
platformOptions | object | No | Platform-specific values for future occurrences. |
Published and processing occurrences are preserved. Future scheduled occurrences are cancelled and regenerated from startsAt.
Attachments are copied to dopost storage and checked with the same publishing rules as the web composer before the series is updated. Blocking errors reject the request; warnings allow it to continue. See Detailed validation errors for the error response and file details.
{
"id": "cm_recurring_123",
"success": true,
"status": "ACTIVE",
"nextRunAt": "2026-10-02T10:00:00.000Z",
"cancelledPosts": 1
}{
"id": "cm_recurring_123",
"success": true,
"status": "ACTIVE",
"nextRunAt": "2026-10-02T10:00:00.000Z",
"cancelledPosts": 1
}Use update_recurring_post. Pass the series ID from list_recurring_posts and a new startsAt value.
Unzoned dates and times (2027-01-20T10:00:00) use the workspace IANA timezone automatically. Dates with Z or an explicit offset retain their instant; dopost converts and stores UTC. Nonexistent local times during a daylight-saving transition are rejected. Include an explicit offset to distinguish repeated local times.
Publish and reschedule requests accept an optional IANA timezone override, such as Europe/Madrid. For recurring posts, timezone selects the series and initial-date timezone and defaults to the workspace timezone. Updating a series retains its existing timezone. recurrence.endDate is the series' final calendar date.
Google Business: only postType: "standard" is supported, with the same text, CTA and image validation as publication. Events, offers and gallery uploads are not recurring types in dopost.