Set the posting schedule
Read and set an account's queue: the weekly posting slots, its timezone, and the next free slot a queued post would take.
A post created with queue: true lands in that slot, so the schedule is what turns a pile of drafts into a cadence. One call reads it, one call writes the slots and timezone; the response always names the next free slot so an agent can tell the person when the post will go out.
Ask in plain words
- "post three times a week on LinkedIn, mornings"
- "when is the next free slot on my Instagram queue"
- "change my posting timezone to Europe/Berlin"
- "queue everything for weekday mornings in New York time"
- "add a lunchtime slot to the Threads queue"
From an agent host (MCP)
No MCP tool yet: call the REST routes below.
From code (REST)
Bearer API key with the scope each call names (auth, OpenAPI).
GET /api/connections/{id}/queue(read scope): The account's queue: posting slots, timezone, and the next free slot.PATCH /api/connections/{id}/queue(write scope): Set the posting slots and timezone.
From a terminal (CLI)
No CLI command yet.
