One request for every network
The PostBoost REST API publishes to every connected network with the same call. You send one POST /{workspaceUuid}/posts with a list of account ids and a version that holds the caption, and PostBoost turns it into a Facebook Page post, an Instagram caption, a LinkedIn post, an X post and so on. When a post is scheduled, each network's requirements, such as X's 280 characters or a network that needs media, are checked before anything is saved, and a request that breaks one comes back as a 422 error. Validate first runs the same checks for any post.
Pick a mode
Most integrations start with drafts: the post appears in the PostBoost calendar and a person reviews it before it goes out. Scheduling needs a date, a time and a timezone; without a timezone the workspace timezone is used. The queue picks the next free slot of the workspace's posting schedule. Publish now sends the post right away.
SDKs and the CLI
The SDKs for Python, Node.js, PHP, Go, Ruby, Java, C# and Rust and the Bash CLI are generated from the same OpenAPI spec as the API reference, so the field names match the curl request. Install commands for each SDK are in the SDK docs. Errors come back as JSON, and repeating a request with the same Idempotency-Key header within 24 hours never creates a second post.
Test safely
Run your first requests as drafts or with Validate first. Neither publishes anything, and drafts can be deleted from the calendar. The duplicate guard refuses a post with the same text for the same account within 24 hours, which protects you from a retry loop posting twice.