Start scheduling posts
<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>
Hands the app's approved posts to the publisher, so each one goes out at its own scheduled time.
The work runs in the background. This endpoint answers 202 with a job_id; poll Get scheduling job to see how it went. A second start for the same app fails with a 409 while the first one is still starting.
Calling it again for the same window normally returns the job already in flight instead of starting a second one, but treat that as best-effort rather than a guarantee: a retry sent in the moment before the job starts running can come back with a new job_id. Nothing is published twice when that happens, because both runs resolve the same automation for a given post.
It takes the posts whose scheduled_at falls in [scheduled_from, scheduled_until) and that aren't handed over yet, which means the posts you approved plus the ones an earlier run couldn't place. A post still in proposal isn't taken at all, so approve it first. A range holding more than 100 such posts fails with a 422; schedule it in smaller ranges.
Placing a post can fail for reasons this endpoint can't check up front, and each one is counted in the job's result rather than failing the request:
- The workspace is on the free plan. Publishing scheduled posts needs a paid workspace plan, and those posts are counted in plan_limited.
- The app has no connected account for the post's platform with publishing permission, or it has more than one. Those posts move to needs_reconnect and are counted there, and a later run picks them up once you fix the connection.
- The post's platform can't be published to at all, or its scheduled time has already passed. Those posts move to failed, which is final.
The social calendar endpoints share two rate limits: 20 requests per minute across creating, editing, deleting and approving posts, and 40 requests per minute across the rest. This endpoint counts against the 40.
<Note>This endpoint accepts a personal API key. Workspace API keys are not authorized for it and are rejected with a 403.</Note>
Path parameters
ID of the app whose social calendar you want.
ID of the app whose social calendar you want.
Request body
Example request
{
"scheduled_from": "2026-09-01T00:00:00Z",
"scheduled_until": "2026-10-01T00:00:00Z"
}Response
The scheduling job that is now running, or the one already in flight for this range.
Example response
{
"job_id": "68a1c4f0d21b4e0a3c77e912",
"status": "pending"
}Changes
No recorded changes to this endpoint across all 1 revision of this API.