POST https://api.usecommune.com/articles/{article}/schedule Production. There is no separate sandbox host.

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.

Path parameters

  • string Required

Request Headers

  • string
  • string Required

Body

  • string(date-time) Required
  • boolean
POST /articles/{article}/schedule
Loading...

Share your request

Use this link to easily share a pre-filled request of this operation. Everything you filled will be shared apart from the authentication fields.

Request URL

https://api-reference.usecommune.dev/explorer/operation/operation-schedulearticle

Send a delete request

It looks like you’re about to send a DELETE request to this API. This type of request carries a risk of permanent and irreversible data loss.

Are you sure you want to continue?
Response
Waiting for a request to be sent.