Create a post

curl --request POST \
  --url https://api.postqueen.ai/public/v1/posts \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "schedule",
  "date": "2026-10-01T09:00:00.000Z",
  "shortLink": false,
  "tags": [],
  "posts": [
    {
      "integration": {
        "id": "YOUR_CHANNEL_ID"
      },
      "value": [
        {
          "content": "Shipping the new calendar today.",
          "image": []
        }
      ]
    }
  ]
}
'

[
  {
    "postId": "cmg1p0s7k0001qz0h4yq2a8r1",
    "integration": "cmg1ozx2c0000qz0h8c7w5v3n"
  }
]

POST

posts

curl --request POST \
  --url https://api.postqueen.ai/public/v1/posts \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "schedule",
  "date": "2026-10-01T09:00:00.000Z",
  "shortLink": false,
  "tags": [],
  "posts": [
    {
      "integration": {
        "id": "YOUR_CHANNEL_ID"
      },
      "value": [
        {
          "content": "Shipping the new calendar today.",
          "image": []
        }
      ]
    }
  ]
}
'

[
  {
    "postId": "cmg1p0s7k0001qz0h4yq2a8r1",
    "integration": "cmg1ozx2c0000qz0h8c7w5v3n"
  }
]

Every request carries the same five fields: type, date, shortLink, tags and posts. One date applies to every channel in the request: a date inside an entry of posts is ignored. To give channels different times, send one request per time. Each entry in posts is one channel, and each item in its value list is one part of the post: the first is the post, the rest are its thread or comments. The request examples on this page show whole requests for Bluesky, Nostr, WordPress and DEV. A step-by-step guide, from finding the channel id to checking the result, is Schedule a post with the API.

`type`

Value	What happens
`schedule`	The post goes out at `date`, in UTC. A `date` that has already passed publishes at once.
`now`	The post goes out at once. `date` is still required, and PostQueen stamps the current minute instead.
`draft`	Saved on the channel’s calendar without publishing. Move it to scheduled later with Change post status.
`update`	Changes existing posts in place, named by `value[].id`, without starting a new publish. The first id must be a post of your workspace, or the request is refused: see Changing or copying a post.

A draft is checked too: the body, each network’s required settings, and that every item has text or media. The network’s rules on length and media are checked only when the post is set to go out (schedule, now and update), and again when you move a draft to schedule with Change post status. So a draft that was accepted can still be refused then.

Two fields that are easy to miss

image is required on every item of value. Send [] for text only. Leaving it out answers 400 with posts.0.value.0.image must be an array.
group deletes. Leave it out for a new post. When it names an existing group, every post of that group that the request does not resend is deleted.
shortLink changes nothing today. It is required, but PostQueen has no link shortener set up, so links stay as written with true too.

Every field, with its type, is in the body schema on this page. Media must be uploaded first. A post’s media path must end in .png, .jpg, .jpeg, .gif, .webp or .mp4, and a video must be ready: see Upload a file.

Link to another post

Write (post:ID) in a content, with the id of another post of your workspace, and PostQueen replaces it with that post’s address on its network when this post is published. Use it to point a new post or a comment at an earlier one:

{ "content": "Part two of our spring menu. Part one: (post:cmg1p0s7k0001qz0h4yq2a8r1)", "image": [] }

The id is a postId from this endpoint’s answer or an id from List posts. The address is read at publish time, so the other post has to be published first. When it has no address by then, or the id is not a post of your workspace, the placeholder is removed and the rest of the text goes out.

Settings by network

settings.__type is always set from the channel, so you may leave it out; what matters is the shape of the rest. Networks without required settings need no settings at all. Every field of every network, with examples: Posting settings by network.

Network	Required settings
Bluesky, Nostr	None
WordPress	`title`, `type` (`posts`, `pages` or another post type from the `postTypes` tool)
DEV	`title`
Hashnode	`title`, `publication`, at least one `tags` entry
Lemmy	`subreddit` list, each with a community and a title
Listmonk	`subject`, `preview`, `list`
Moltbook	`submolt`
X	`who_can_reply_post`, or `article_title` and `article_status` for an article
Instagram	`post_type`
YouTube	`title`, `type`
TikTok	Eight fields, from `privacy_level` to `content_posting_method`: see TikTok settings
Facebook, Threads	None
Reddit	`subreddit` list, each with a subreddit, title, type and flair choice
Pinterest	`board`
Dribbble	`title`
Discord, Slack	`channel`
Skool	`group`, `label`, `title`
Whop	`company`, `experience`
MeWe	`postType`, and `group` for a group post
Farcaster	`subreddit` list of channels
Google Business Profile	None; an event or offer needs `eventTitle`, `eventStartDate` and `eventEndDate`
LinkedIn, Mastodon, Telegram, VK, Kick, Twitch, Tumblr	None

What comes back

A 201 with one row per channel entry. Keep the postIds: the other post endpoints take them.

[{ "postId": "cmg1p0s7k0001qz0h4yq2a8r1", "integration": "cmg1ozx2c0000qz0h8c7w5v3n" }]

When a part breaks a network’s rule, the call answers 400 before anything is saved, naming the network and the channel:

{
  "statusCode": 400,
  "provider": "bluesky",
  "name": "PostQueen",
  "message": "post is too long, please fix it"
}

A channel id that is not a channel of your workspace, or a channel that was deleted, answers 400 with Integration with id <id> not found, and nothing is saved. Take the ids from List channels. Every status the endpoint returns, and what to do about it, is on Limits and errors.

Changing or copying a post

Change a scheduled post. Send it again with value[].id set to the id of each part you keep, and its group from List posts so the parts you leave out are deleted. Use update with the post’s current date to change its text or media without touching the schedule, or schedule with a new date to move it. To change only its settings, Update post settings is simpler.
update needs the id of the main post. In each entry of posts, value[0].id must be the id of a post in your workspace, and of the post itself, not of one of its comments. A missing, mistyped or deleted id is refused with 400 before anything is saved:
type 'update' changes an existing post: value[0].id must be the id of a post in this workspace (the main post, not a comment). To create a post, use type 'draft', 'schedule' or 'now'.
Take the ids from List posts. Later items of value with a new id, or none, are added to the post as new comments or thread items.
Publish a post again. schedule or now with the id of a post that was already published is refused with 400. Add "republish": true if you mean it.
Copy a post. There is no copy endpoint. Read the post with List posts, parse its settings and image (they come back as JSON strings), and send the content as a new post without any post ids or group.

Size and rate limits

Do not put file data in the body. This endpoint takes about 100 kB of JSON, which one base64 image exceeds, and answers 413 before anything is checked. Upload the file first and send its id and path.

A workspace can send 30 POST /posts requests an hour. A request refused with 400 during validation, such as a missing setting or a post that is too long, gets its slot back. A refusal once the posts are being created, such as a republish without republish or “Media not found”, counts. One request can carry many channels and a whole thread, and it counts once. See Limits and errors.

Authorizations

Authorization

string

header

required

Your API key from Connections > API Keys, or an OAuth access token (pos_...). Send it as it is, with no Bearer prefix.

Body

application/json

type

enum<string>

required

schedule queues the post for date, and publishes it at once when date has already passed. now publishes at once. draft saves it without publishing. update changes posts named by value[].id without starting a new publish. Its value[0].id must be the id of a main post of the workspace, not of a comment, or the request is refused with 400

Available options:

draft,

schedule,

now,

update

date

string<date-time>

required

Publish date and time in UTC, ISO 8601. Required for every type; now uses the current minute instead. A date in the past with schedule publishes at once. It applies to every entry in posts: a date inside an entry is ignored

shortLink

boolean

required

Replace links in the text with PostQueen short links. Required; send false to keep links as they are. PostQueen has no link shortener set up today, so true leaves links as they are too

Response

Saved. One row per channel entry

postId

string

integration

string

Last modified on October 9, 2026

Get started

Endpoints

Posting settings by network

Build on PostQueen

SDK and no-code

`type`

Two fields that are easy to miss

Link to another post

Settings by network

What comes back

Changing or copying a post

Size and rate limits

Authorizations

Body

Response

​type

​Two fields that are easy to miss

​Link to another post

​Settings by network

​What comes back

​Changing or copying a post

​Size and rate limits

Authorizations

Body

Response

`type`

Two fields that are easy to miss

Link to another post

Settings by network

What comes back

Changing or copying a post

Size and rate limits