Skip to main content
Scheduling, media and analytics are all public API calls, which is why agents drive her so well. REST at https://api.postqueen.ai/public/v1, with your API key in the Authorization header. That key is the only setup: your first scheduled post is one POST away.
POST /public/v1/posts: the request body and the 201 response with the scheduled post ids

SDKs & Integrations

NodeJS SDK

Call the API from Node with the official typed client.

n8n Node

Drop the community node into any workflow, no code needed.

Zapier

Wire posts into thousands of apps with a webhook and your key.

Make

Call her from any scenario with the built-in HTTP module.

Webhooks

She calls your endpoint the moment a post goes live.

RSS AutoPost

She reads the feed hourly and turns the newest item into a draft.

Authentication

Two ways to authenticate, and both ride in the same Authorization header:

API Key

Get your API key from Settings > Developers > Public API. You will see the Developers tab if you are an organization admin on a plan that includes the public API. Include the key in the Authorization header:

OAuth2 Token

Building an app for other PostQueen users? Use OAuth2 Authentication to get tokens that act on behalf of users, so nobody has to hand over an API key. OAuth tokens start with pos_ and are used the same way:

Which one you want

Both reach the same endpoints. The difference is whose account you are acting on.
An API key has no expiry and nothing rotates it on a schedule. It stops working when you regenerate it and not before, so treat it as a password rather than a session.

Base URL

Rate Limits

30 requests per hour limit applies only to the create post endpoint.That is not a ceiling of 30 posts. Each call counts once no matter how much it carries, so put several posts in one request when you need volume.
The rate limit is one global value for the whole instance, and it is the same on every subscription plan. Plans differ on channel counts and posts per month instead. Self-hosting? You set the per-hour limit with the API_LIMIT env var. The official Docker Compose sets API_LIMIT: 30; with the variable unset the backend defaults to 90 requests per hour. Full env var list: Configuration Reference.

Errors

For DELETE endpoints, you can treat 404 as already deleted: the row is gone either way, so it is safe to ignore. A 500 can mean the same thing today because of a known issue where a missing post ID surfaces as 500 instead of 404, but only if the error matches that specific signature. Treat other 500 responses as real server errors: log them, retry with exponential backoff, and do not swallow them quietly.

Terminology

The PostQueen UI uses the term channel, while the API uses integration. They refer to the same thing: a connected social media account.

Generate Output

Let the app write the JSON for you. It is the same composer you use to schedule a post, except it stops one step short: instead of putting the post on your calendar, it hands over the payload for your API request.
  • For cloud, make sure you are logged in.
  • For local, make sure your PostQueen server is running and you are logged in.

Supported Platforms

She posts to 30+ networks, and each one has its own settings schema. Every post you send carries a settings object. It usually names the provider in a __type field, though the server overwrites that field with the provider of the channel you addressed, so what has to match your channel is the shape of the settings, not the string you put in __type. Channels whose provider needs no settings can send an empty object.

Platforms with custom settings

The Farcaster identifier is spelled wrapcast, not warpcast. That is what GET /integrations returns and what the settings schema is keyed on. On POST /posts the server replaces whatever you put in __type with the connected channelโ€™s own identifier, so a wrong spelling is not rejected, it is simply ignored.

Platforms without custom settings

These platforms only require { "__type": "platform-name" }:

View Provider Settings Reference

Every setting each platform accepts, with a worked example.

Quick Examples

Schedule a post to X (Twitter)

Post immediately to LinkedIn

Upload an image and post to Instagram

Publish a Medium article

Create a Google My Business offer

Next steps

Schedule your first post

The create endpoint, field by field, with a worked request.

Find your channel IDs

Every connected channel, with the id every other call needs.

Use the typed client

@postqueen/node, where each method maps to one endpoint.

Build for other people

OAuth2 tokens that act on your usersโ€™ behalf, so nobody hands over a key.