Create Recurring Post
Create a recurring social media post series.
Create a recurring social media post series.
/api/v1/recurring-postCreate a recurring post and schedule its first occurrence.
{
"accountId": "<accountId>",
"text": "A useful weekly update from dopost",
"startsAt": "2026-09-25T10:00:00Z",
"timezone": "Europe/Madrid",
"recurrence": {
"frequency": "WEEKLY",
"interval": 1,
"weekdays": [5],
"endType": "AFTER_OCCURRENCES",
"occurrenceCount": 8
}
}{
"accountId": "<accountId>",
"text": "A useful weekly update from dopost",
"startsAt": "2026-09-25T10:00:00Z",
"timezone": "Europe/Madrid",
"recurrence": {
"frequency": "WEEKLY",
"interval": 1,
"weekdays": [5],
"endType": "AFTER_OCCURRENCES",
"occurrenceCount": 8
}
}| Field | Type | Required | Description |
|---|---|---|---|
accountId | string | Yes | Connected social account ID. |
text | string | Conditional | Post text. Required when media is empty. |
media | string[] | object[] | Conditional | Up to 10 public media items. Required when text is empty. |
startsAt | string | Yes | First occurrence as ISO 8601, at least two minutes in the future. |
timezone | string | No | IANA timezone. Defaults to the workspace timezone. |
recurrence | object | Yes | Recurrence rules described below. |
platformOptions | object | No | The same platform options accepted by Publish Post. |
| Field | Type | Required | Description |
|---|---|---|---|
frequency | DAILY | WEEKLY | MONTHLY | Yes | Recurrence frequency. |
interval | integer | No | Repeat every N units, from 1 to 365. Defaults to 1. |
weekdays | integer[] | For weekly | Days from 0 (Sunday) through 6 (Saturday). |
endType | NEVER | ON_DATE | AFTER_OCCURRENCES | No | Defaults to NEVER. |
endDate | string | For ON_DATE | ISO 8601 end date. |
occurrenceCount | integer | For AFTER_OCCURRENCES | Total occurrences, from 2 to 500. |
Attachments are copied to dopost storage and checked with the same publishing rules as the web composer before the series is created. Blocking errors reject the request; warnings allow it to continue. See Detailed validation errors for the error response and file details.
{
"success": true,
"recurringPostId": "cm_recurring_123",
"postId": "cm_post_123",
"nextRunAt": "2026-09-25T10:00:00.000Z",
"status": "ACTIVE"
}{
"success": true,
"recurringPostId": "cm_recurring_123",
"postId": "cm_post_123",
"nextRunAt": "2026-09-25T10:00:00.000Z",
"status": "ACTIVE"
}The first post is scheduled for startsAt; subsequent posts follow the configured recurrence.
Use create_recurring_post with the same values. The tool exposes recurrence fields at the top level so an agent can fill them without constructing a nested object.
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.