Skip to main content
The public API does what the app does with posts: schedule and publish them on your channels, upload media, read analytics and manage channels. It is plain HTTPS and JSON, and everything in it acts on one workspace.
A new blog post from an RSS trigger goes to PostQueen with POST /public/v1/posts, and PostQueen posts it to X, LinkedIn and Bluesky

A first request

1

Copy your API key

Where the API key is: in the app, open Connections > API Keys. Only a workspace Admin or Super Admin can reveal or rotate it; other members see it masked. A workspace has one key, and each agent card on Connections shows your MCP address with the key already filled in.
2

List your channels

3

Read the answer

Each channel comes back with an id. That id is what you pass to create a post, read analytics or run a tool.
A list of channels, even an empty one, means the key works. A 401 names what is wrong: see Limits and errors.
The next step, from here to a post on the calendar, is Schedule a post with the API.

Authentication

Every request to /public/v1 carries one header:
The value is the key itself. Adding Bearer in front makes it an invalid key. The key belongs to the whole workspace and has no expiry: it works until an admin rotates it under Connections > API Keys, which ends the old key at once. Treat it as a password. If you are building a product that other PostQueen users connect to, do not ask them for their key. Register an OAuth app: they approve it on a consent screen, and you get a pos_ token that goes in the same header, also with no prefix. Who am I tells either one which workspace it acts on, and for an OAuth token who approved it.

Channels and integrations

The app says channel, the API says integration. They are the same thing: one connected account on one network. So GET /integrations lists your channels, and integration.id in a post is a channel id. Each network has an identifier, such as bluesky, wordpress or devto, returned as identifier by List channels. A post’s settings follow that network’s shape: Posting settings by network. How each network connects is on Channels.

What you can do

Channels

List, connect and delete channels, read their settings and run their helper tools.

Posts

Schedule, publish now, save drafts, list, change and delete posts.

Media

Upload images and videos from disk or from a URL, and list the media library.

Analytics

Channel metrics, one post’s metrics, and ranked lists and totals.

Posting settings by network

The settings a post takes on each network, with examples.

OAuth apps

Let other PostQueen workspaces sign in to your product.

Limits

A workspace can send 30 POST /posts requests an hour, not counting requests refused during validation, and each upload endpoint allows 300 requests an hour. Nothing else is limited. One request can carry many channels and a whole thread and counts once, so batch posts rather than sending them one by one. Details, headers and every status code: Limits and errors.

Tools that use the API

Node.js SDK

@postqueen/node, a typed client for the most used endpoints.

n8n

The PostQueen community node, in any n8n workflow.

Zapier and Make

Coming soon. Until then, call the API from their HTTP steps.

Webhooks

PostQueen calls your URL when a post is published.
Last modified on October 9, 2026