Skip to main content
GET
List unpublished drafts
Saved drafts are available to all users. Normal publishing and scheduling rules apply when submitting. Drafts stay separate from scheduled and published posts. Saving does not publish or use your posting allowance. Text, media, destinations, and platform settings can be unfinished. Use the draft UUID from the save response. Read the draft’s current revision before editing, deleting, or submitting, then send it as expected_revision. A 409 means the draft changed or was submitted; read it again before continuing. Only the submit endpoint publishes or schedules. It runs the same account, plan, content, and platform checks as Create Post. If validation fails, the draft stays saved. After a successful submission, the draft read includes submission with the original jobs. Repeating the same submission revision and schedule returns those same jobs. Use profile_id for a non-default connection profile. A draft uses one profile. Lists include only unpublished drafts in that profile. See the draft workflow for dashboard, API, MCP, and CLI examples.

Authorizations

Authorization
string
header
required

Use Authorization: Bearer {api_key}

Query Parameters

profile_id
string

Omit to use the default profile on lists. On reads, deletes and submissions, optionally verify the draft belongs to this profile. Random public connection profile ID returned by GET /api/v1/profiles.

Pattern: ^[A-Za-z0-9]{6,32}$
Example:

"AbC123xYz90"

page
integer
default:1
Required range: 1 <= x <= 100000
per_page
integer
default:20
Required range: 1 <= x <= 100

Response

Success

status
enum<string>
Available options:
ok
data
object
Last modified on October 9, 2026