Solution

Embedded social publishing for SaaS products

Let customers connect social accounts and publish from your app while UniPost handles the cross-platform publishing infrastructure.

See pricing
Primary query:social media API for SaaS
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 workflows
Customer accounts
Product-tier pricing
White-label 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.

Connect customer accounts

Create hosted connection sessions from your backend and attach returned account_ids to your own users.

  • Support multi-tenant workspaces.
  • Keep customer account ownership clear.
  • Use webhook events for disconnects and token issues.

Publish or schedule posts

A SaaS workflow often includes drafts, approvals, billing checks, and scheduled publishing before the final API call.

  • Publish only after your product approves the content.
  • Attach metadata for audit trails.
  • Track results in your own activity feed.

Handle webhooks and errors

Handle webhooks and errors centrally so support teams can explain platform-specific failures without reading native docs.

  • Show user-friendly failure reasons.
  • Keep retry decisions in your backend.
  • Record platform-specific differences in customer history.

Honest limitations

  • Your SaaS still owns tenant permissions, billing gates, and content approval policy.
  • Native platform app review may be required when using customer-owned credentials.

Related paths

Create post APIPricingCompare vendorsPlatform requirements matrix
FAQ

Common evaluation questions

Can I embed account connection?

Yes. Hosted Connect is designed for customer account connection inside SaaS products.

Can I bill my own customers separately?

Yes. UniPost is infrastructure; your product owns customer packaging and pricing.

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