Social Media Publishing API

A social media publishing API for embedded workflows

Embed social publishing into your product with the primitives product teams need: customer account connection, media handling, scheduling, status tracking, and reliable delivery feedback.

See pricing
Primary query:social media publishing API
POST /v1/postsUniPost API
await fetch("https://api.unipost.dev/v1/posts", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${UNIPOST_API_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    caption: "Approved by the customer",
    account_ids: ["sa_facebook_123", "sa_linkedin_456"],
    publish_mode: "scheduled",
    scheduled_at: "2026-07-02T13:30:00Z",
    metadata: { source: "customer_approval_flow" }
  })
});
Embedded SaaS workflows
Hosted Connect and white-label modes
Approval-friendly publishing primitives
Docs and pricing CTAs on every path
Workflow

From connected account to published post

These are the same primitives whether you are building a scheduler, SaaS workflow, AI agent, or white-label social publishing layer.

STEP 1

Connect customer accounts through hosted OAuth or customer-owned credentials.

STEP 2

Upload or reference media before publishing so platform validation is centralized.

STEP 3

Publish or schedule posts with POST /v1/posts using account_ids for each destination.

STEP 4

Track results through post status, analytics, and webhooks.

STEP 5

Handle webhooks and errors with platform-specific messages instead of generic failures.

Designed for embedded publishing

UniPost works for SaaS products that want social publishing inside their own workflow instead of sending customers to another dashboard.

  • Create account connection sessions from your backend.
  • Store account_ids against your own users or workspaces.
  • Publish after your own approval, billing, or content generation flow.

Status tracking for product teams

Publishing is an operational workflow. UniPost exposes status and webhooks so your UI can explain what happened.

  • Show pending, scheduled, posted, and failed states.
  • Record platform IDs for downstream analytics.
  • Use webhook events to sync your own activity feed.

Honest platform constraints

A publishing API should make platform constraints visible instead of hiding native requirements until production.

  • Different platforms expose different media and analytics features.
  • Native app review can be required for customer-owned credentials.
  • Some networks change policy or rate limits without much notice.

Honest limitations

  • UniPost cannot bypass native platform review, permissions, or content policy.
  • White-label OAuth depends on each customer or tenant having approved platform credentials where required.
  • Some advanced native features may need dedicated platform-specific support before they become unified fields.

Related paths

Create post APIPricingCompare vendorsPlatform requirements matrix
FAQ

Common evaluation questions

Is a publishing API different from a posting API?

Posting is the API call. Publishing includes the broader workflow: account connection, media, scheduling, approvals, status, analytics, and webhooks.

Can I embed this inside my SaaS?

Yes. UniPost is designed for products that want customers to connect accounts and publish without leaving the product experience.

Can I remove UniPost branding?

Growth and higher plans support native or white-label flows for supported platforms where your own credentials are approved.

Ship social publishing without rebuilding every native API.

Start with the docs, test on the free plan, then choose the pricing tier that fits your usage.

Pricing