Schedule an article
Queues this article to go out at a time you choose.
Only a draft or an already scheduled article can be scheduled, and scheduled_for has to be in the future. Scheduling an already scheduled article moves it, which is how a send time is changed: there is no separate reschedule.
A scheduled article is not published. Its status becomes scheduled and posted_at stays null, so it stays invisible on every reader surface until it goes out. The newsletter's own credentials can read it, which is how you check what is queued.
Every gate Send an article to the list (POST /articles/{article}/send) runs is run here, so a missing footer, an unreachable image, an unverified sending address or an empty body refuses the schedule now rather than failing silently at six in the morning.
The time is honoured to within a few minutes, not to the second. Commune dispatches queued articles in passes, so scheduled_for is the moment from which an article may go out rather than the moment it will.
Publishes article.scheduled.
Request
- Base URL: https://api.usecommune.com
- URL: https://api.usecommune.com/articles/{article}/schedule
- Auth: one of:
- HTTP bearer
- OAuth 2 (authorization code, authorization URL https://usecommune.com/api/oauth/authorize, token URL https://usecommune.com/api/oauth/token, scopes: sending:write)
Request body
Example request
{
"scheduled_for": "2026-10-01T09:00:00Z"
}Response
The article, as it now stands: status is scheduled and scheduled_for is the time it will go out from.
Example response
{
"short_id": "k7Rm2xQp",
"newsletter": {
"object": "newsletter",
"id": "9a4c1c6e-0f2b-4f47-9d3f-6d1b1a2c3d4e"
},
"authors": [
{
"object": "newsletter",
"id": "9a4c1c6e-0f2b-4f47-9d3f-6d1b1a2c3d4e"
}
],
"thread": {
"object": "newsletter",
"id": "9a4c1c6e-0f2b-4f47-9d3f-6d1b1a2c3d4e"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.