Publishing
Publish a content container immediately or schedule it for a future time, then track the resulting posts.
Two write endpoints kick off a publish: POST /v1/content/:containerId/publish sends now, POST /v1/content/:containerId/schedule queues it for a scheduledFor timestamp. Both create the same sp_<uuid> post records — publish-now rows just have scheduledFor equal to the moment they were issued. Everything after that (get, list, reschedule, cancel) acts on those post records regardless of which endpoint created them.
If this is your first publish, start with publish-content — fewer fields to get right, immediate feedback. Layer in schedule-content when you need to queue posts ahead of time.
In this section
POST publish
Publish a container now. Atomic batch up to 50 targets.
POST schedule
Queue a container for a future scheduledFor. Same target shape as publish.
GET post
Read a single post by scheduledPostId. Polling cadence guidance.
GET posts
List posts in a project. Filter by status, platform, time window.
POST reschedule
Change scheduledFor on a queued post.
DELETE cancel
Cancel a queued post before it starts publishing.
POST notify-device
SMS-to-device fallback when the creator finishes on-platform.
GET tiktok-music
List TikTok-licensed tracks for the tiktokMusic.manual mode.