Skip to main content
A single HTTP API for publishing to X (Twitter), Instagram, LinkedIn, Facebook Pages, Threads, Pinterest, and Bluesky. Every post runs through a preflight validator before the upstream call, every error response carries the rule that fired, and every write accepts an idempotency key.

Quickstart

Publish your first tweet via curl in 90 seconds.

Authentication

Bearer keys, scoping, rotation.

Errors

The twelve error codes and what each one means.

Preflight

Every documented platform constraint, checked before the upstream call.

​
What you can do

Small, opinionated API surface — one primitive done well. 
POST   /v1/posts                          publish or schedule a post
GET    /v1/posts                          list posts (filterable, cursor-paginated)
GET    /v1/posts/:id                      full post record + every attempt

POST   /v1/media                          multipart upload, returns med_… id
GET    /v1/media                          list uploaded media

POST   /v1/accounts/connect/:platform     start an OAuth handshake
POST   /v1/accounts/connect/:platform/complete   finish it
GET    /v1/accounts                       list connected accounts
DELETE /v1/accounts/:id                   disconnect

POST   /v1/webhook-endpoints              register a webhook URL
POST   /v1/api-keys                       mint a scoped API key
The full request and response shapes live in the API reference.

​
Built for

AI agents

n8n, LangGraph, CrewAI, Make. Idempotent, MCP-compatible, no per-profile pricing.

Indie cross-posting tools

The wedge for anyone hand-rolling integrations because every existing scheduler is per-channel-priced.

Agencies on n8n / Postiz

Migrate off Hootsuite / Sprout / Later to a flat-priced primitive that fails loudly.

​
Principles

These are non-negotiable. If a feature breaks one of them, the feature loses.
Every documented platform constraint is checked before we touch the upstream API. A 312-grapheme Bluesky post fails locally with a rule id, not asynchronously with body: {}.
No empty bodies. Every failure includes a stable code, the rule that fired, the upstream response, and a remediation hint. See errors.
Every write accepts Idempotency-Key. Retries are safe. See idempotency.
When LinkedIn sunsets an API version, we upgrade internally and publish a changelog. Your workflow doesn’t break at 2 a.m.

​
Status

The API surface is identical across every platform — same POST /v1/posts, same error envelope, same idempotency contract. Each platform’s launch is gated on its own developer-portal review; approvals clear at different rates. Twitter and Bluesky are live for every signup today. The rest (Instagram, LinkedIn, Facebook, Threads, Pinterest) ship as approvals clear — track the changelog and the public version tracker at GET /v1/platform-versions.