Solution

Social media scheduler API infrastructure

Use UniPost to power calendars, queues, approvals, retries, and scheduled publishing without rebuilding native social APIs.

Read posting docs
Primary query:social media scheduler 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: "New feature is live",
    account_ids: ["sa_instagram_123", "sa_threads_456"],
    media_urls: ["https://cdn.example.com/launch.mp4"],
    platform_options: {
      instagram: { type: "reel" },
      threads: { reply_control: "everyone" }
    }
  })
});
Calendars
Queues
Scheduled posts
Webhook status
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

A scheduler starts with account connection. Hosted Connect gives each customer a path to authorize destinations.

  • Store account_ids in your scheduler.
  • Group destinations by customer workspace.
  • Refresh and account events arrive through webhooks.

Upload or reference media

Media can be uploaded or referenced before a calendar item is published.

  • Validate asset readiness early.
  • Preserve platform-specific variants.
  • Avoid re-uploading unchanged assets.

Publish or schedule posts

Publish immediately or schedule future delivery through POST /v1/posts.

  • Attach scheduled_at to queued content.
  • Use status updates to keep the calendar honest.
  • Handle webhooks and errors in your queue worker.

Honest limitations

  • platform-specific differences still matter for video length, thumbnails, captions, and link rendering.
  • Recurring queue logic belongs in your product unless you choose to model each occurrence as a UniPost post.

Related paths

Create post APIPricingCompare vendorsPlatform requirements matrix
FAQ

Common evaluation questions

Can UniPost power a calendar UI?

Yes. UniPost handles publishing primitives while your product owns the calendar and approval UX.

Can I retry failed scheduled posts?

Yes. Use status and webhook events to decide whether to retry, edit, or notify the customer.

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