Queue a post for a later time

Rules are checked NOW, not at send time: a disconnected network or missing media is rejected while you build the flow rather than silently failing overnight. The Free plan keeps 3 scheduled posts waiting at a time: past that the post is not refused but saved as held (202, code queue_limit, with an upgrade link) and scheduled automatically when the plan is upgraded; it is never published on Free and can be canceled. On Free only the first 2 networks of a post are published when it runs; the answer names the others in held_networks. run_at "next_slot" puts the post in the brand's next free queue slot (GET/PUT /api/brands/{id}/slots); the Free queue cap applies the same way.

post/api/schedule

Request

  • Base URL: https://postwire.io
  • URL: https://postwire.io/api/schedule
  • Auth: HTTP bearer

Request body

platformsstring[] required
textstring
run_atstring required

When to publish: an ISO 8601 time in the future (up to 365 days), or "next_slot" for the brand's next free queue slot. A post goes to the earliest slot that every one of its networks has and that none of them already uses for another waiting (queued, held or publishing) post of the same brand. When its networks share no slot, it goes to the earliest slot of any of them that is free for all. Slots less than 2 minutes away are skipped; the search looks 28 days ahead. The answer then carries slot { run_at, timezone, local, shared }.

video_urlstring uri
brand_idstring uuid
labelstring
timezonestring

With run_at next_slot: the IANA timezone to read the slots in when the brand has none saved (e.g. America/Lima). Default UTC. Not stored with the post.

Example request

{
  "run_at": "next_slot"
}

Response

{ ok, scheduled: {...}, targets[], message, held_networks?, held_message?, upgrade? }

Changes

No recorded changes to this operation across all 1 revision of this API.