The social media API

One API to connect, publish, and track every social platform.

PostGate is the API layer for social publishing: connect Instagram, Facebook, LinkedIn, TikTok, YouTube, Threads, Bluesky, Mastodon, Telegram, Pinterest, Google Business Profile, and X once, then send content through a single POST /api/posts call. Every target — each platform destination on a post — carries its own status, attempt count, error detail, and permalink, so your product knows what actually happened instead of assuming a 202 Accepted means published.

Why this matters

Twelve platforms, twelve sets of quirks — one API absorbs them

One integration instead of twelve

Each platform has its own OAuth flow, media rules, and publishing endpoint. PostGate connects accounts through profiles and normalizes publishing behind one resource model, so adding a new platform to your product doesn't mean writing a new provider integration.

Delivery evidence, not just acceptance

A create-post response is acceptance, not proof. The targets array is the operational truth for every destination: status, attempt count, next retry, error, and platform ID. Subscribe to signed webhooks for terminal state instead of polling.

Built for teams and platforms, not solo posting

Scoped API keys, profile groups for tenant isolation, and white-label environments mean PostGate works the same whether you're publishing for one brand or building a product on top of it for thousands.

How it works

Connect, publish, and observe — the same three steps for every platform

01

Connect accounts as profiles

Customers authorize a platform once through OAuth. Each connected account becomes a profile ID you target deterministically — no inferred account matching.

02

Publish through one endpoint

POST /api/posts takes a body, a list of profile IDs, and optional media and platform-specific options under post.options.<platform>.

03

Read status or subscribe to events

Poll GET /api/posts/{id} for target-level status, or subscribe to post.published, post.partial, and post.failed webhooks.

Go deeper

Two more ways to think about the same API

Multi-platform posting API

How one request shape delivers to many platform targets independently, with per-target status instead of an all-or-nothing result.

Social publishing API

Why PostGate models publishing as a lifecycle — draft, scheduled, and per-target delivery — instead of a single fire-and-forget post.

Get started

Build against the free sandbox plan

Free, Solo, Launch, and Build plans all include the full API — connecting profiles, publishing, media, schedules, and webhooks. The difference is connected profiles, posting volume, and entitlements like white-label and BYOK.