Post Scheduling
Post Scheduling
The same calendar you use in the product. A post can go to one connected account or to several at once. Saving it does not publish it. Confirm does.
What you are scheduling
In the product this is a post in Compose, then a row on the calendar. The API calls that row a post group: one shared caption, plus a target for each account that should receive it. LinkedIn, Instagram, Facebook, X, and the other networks you have already connected are targets. You do not connect an account through the API. Connect it in the product, then list it.
A group has two moments. POST /api/v1/scheduling/post-groups saves a draft and does not charge. POST /api/v1/scheduling/post-groups/{id}/confirm checks that every target is ready, puts the post on the calendar, and charges the same schedule fee as the app (or uses the free allowance).
The three kinds of post
type is promotion (the usual post; this is the default), knowledge_post (a post that should stay close to a Knowledge Vault fact), or comment_reply. A comment reply is accepted on a draft and refused when you confirm, because a reply is not placed on the calendar. Use promotion unless you mean the other two.
Guides
- Accounts — which connected profiles you can target
- Drafts — create, read, edit, and cancel before confirm
- Confirm — publish onto the calendar, reschedule, and the errors that stop a charge
OpenAPI: /openapi/scheduling-v1.yaml. Agents that should schedule without writing HTTP can use MCP. The MCP tool scheduling_schedule_post creates the draft and confirms it in one call, so it charges. The REST create call does not.