Social Media API for SaaS

Social media API for SaaS products adding publishing workflows

Add social publishing to your SaaS without per-account pricing eating the margin. Every paid plan includes unlimited connected accounts.

Add social publishing, OAuth account connection, status tracking, and client-facing dashboards to your SaaS without turning platform integrations into your roadmap.

Last updated: November 2026

One API keyNo per-account fees15 platformsAPI key authScheduled publishingOfficial APIs838k+ connected accountsDirect engineer support

Quick start
const response = await fetch("https://api.bundle.social/api/v1/post", {  method: "POST",  headers: {    "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,    "Content-Type": "application/json"  },  body: JSON.stringify({    // Isolate posts per customer using teamId    teamId: "customer_workspace_889",    title: "Customer scheduled post",    postDate: "2026-05-14T10:00:00.000Z",    status: "SCHEDULED",    socialAccountTypes: ["LINKEDIN", "TWITTER"],    data: {      LINKEDIN: { text: "Excited to share our new integration." },      TWITTER: { text: "Integration is live." }    }  })});

What SaaS teams end up maintaining

  • Customer-facing products need OAuth, permissions, status, errors, and support visibility on top of a publish endpoint.
  • Every new platform creates support tickets when native account rules do not match the product UX.
  • The dashboard, retry workflow, and account model often take longer than the first API call.

What bundle.social handles

  • Expose social publishing in your SaaS while bundle.social handles account connection and platform variance.
  • Use API automation for your backend and dashboard views for customer success or operations teams.
  • Scale from one platform to many without reworking the product model each time.

Your SaaS owns the workflow, bundle.social runs the integrations

Your product keeps the composer, the calendar and the customer accounts. bundle.social stores the OAuth tokens, publishes to each platform and reports per-platform status and errors back to your backend.

How it works

Connect accounts once, then create and schedule posts with channel-specific fields from one API.

  1. 01

    Create a team per customer

    Call POST /api/v1/team when a customer workspace is created and store the returned team ID. That customer's accounts, posts and uploads live in the team.
  2. 02

    Connect customer accounts

    POST /api/v1/social-account/create-portal-link returns a hosted connect URL for the team. bundle.social stores and refreshes the platform tokens.
  3. 03

    Publish and track status

    Schedule posts with POST /api/v1/post and listen for the post.published webhook, which reports POSTED or ERROR for each post.

Build social media workflows without rebuilding every platform

Social media API for SaaS products that need embedded workflows

A social media API for SaaS matters when publishing is part of your product but not infrastructure your team wants to maintain. Customers expect connected accounts, a content editor, scheduled posts, media uploads, analytics, approval flows and readable errors. Each platform has its own permissions, limits, media rules and review requirements, so keeping every native integration in-house turns into a roadmap of its own.

With embedded publishing the customer stays inside your SaaS to connect accounts, create content, schedule posts and check status. That suits marketing platforms, creator tools, agency dashboards, CRM systems, AI content generators and vertical SaaS products. Your product decides how content is created, how clients approve it and how workspaces are organized; the API sits underneath.

What fails in production, and who sees it

A post can fail because of account permissions, media rules, platform review, token expiry, invalid fields, processing delays or customer-specific setup. Once your product exposes publishing, each of those failures arrives as a support ticket for your team.

bundle.social records the failure on the post, per platform, and sends it to your webhook. Your UI can show the customer a readable message, and your support staff can open the same post in the bundle.social dashboard without asking engineering to dig through logs.

Decide the product model before the first customer connects

Define how customers, teams, permissions and connected accounts relate before you ship. An MVP may need one user and one social account, but real customers bring several workspaces, brands, clients, approvals and roles. Retrofitting that after accounts are connected is slow.

Decide early whether you need immediate publishing, scheduled publishing, media workflows, analytics, post history or support visibility, because each one changes the build. A basic post is one backend call. A production scheduler also needs status tracking, time zones, retries and clear error messages.

From one channel to a full SaaS social layer

Many SaaS products start with one channel and a simple scheduling use case. Once customers adopt it, they ask for Instagram, TikTok, LinkedIn, Facebook, YouTube, Google Business Profile, approvals, client reporting, bulk imports and AI-generated drafts.

You can start with account connection and post creation, then add scheduling, media uploads, analytics, comments, webhooks and post history as the product matures. The request shape stays the same across platforms, and platform-specific fields are there when your product needs native control.

What a SaaS customer wrote about the integration

Drew, reviewing bundle.social on Trustpilot in March 2026: "Reliable and well documented API with great support. Made integration into my niche SaaS offering a breeze."

Embedding walkthrough

How to embed social publishing in a SaaS product

Six steps take a new customer workspace to a published post. The developer example on this page runs the same calls in order.

1. Create a team for each workspace

POST /api/v1/team with a name of 3 to 80 characters. Save team.id next to your workspace record, because almost every later call needs it as teamId. The Free plan allows 3 teams; Pro and Business have no team cap.

2. Connect the customer's accounts

POST /api/v1/social-account/create-portal-link returns a url for a hosted connect page limited to the socialAccountTypes you pass. The link expires after 10 minutes unless you set expiresIn (5 to 2880 minutes). To keep the connect screen inside your UI, call POST /api/v1/social-account/connect per platform; it returns the platform OAuth URL.

3. Upload media

POST /api/v1/upload accepts a multipart file and POST /api/v1/upload/from-url fetches a public URL. Both return an upload ID for uploadIds.

4. Save drafts or schedule

POST /api/v1/post with status DRAFT or SCHEDULED, a postDate, and one data block per platform. Pass your composer ID as referenceKey (up to 128 characters) and read the post back with GET /api/v1/post/reference-key/:referenceKey.

5. Show status in your UI

The post.published webhook fires when a post ends as POSTED or ERROR. Its data is the full post, with a message per platform in errors and the live permalink in externalData. GET /api/v1/post/:id returns the same object on demand.

6. Edit, retry or cancel

PATCH /api/v1/post/:id changes a post while it is DRAFT or SCHEDULED. After you fix the cause of a failure, POST /api/v1/post/:id/retry publishes it again. Deleting a scheduled post cancels it; deleting a published one leaves it live on the platform.

SaaS-ready social publishing building blocks

Account connection, post creation, status tracking, media, analytics, and dashboard workflows designed for product teams.

Customer account connection

Generate connect URLs and let users authorize social accounts without your product storing OAuth tokens. bundle.social stores and refreshes the tokens.

Server-side publishing API

Create posts from your backend with an organization API key. Each customer's accounts and posts stay in its own team, addressed by teamId.

Operational dashboard

Support and marketing teams can inspect accounts, posts, errors, and scheduled content outside your app, so they can resolve customer issues without pinging engineering.

Analytics expansion path

Add reporting and imported post history to your SaaS once publishing is live. Analytics endpoints need a paid plan.

Developer example

Social media API for SaaS: full embedding example

Examples use bundle.social's public API shape: API key authentication, a post date, selected social account types, and platform-specific data.

TypeScript
// Server-side helper. Keep the API key on your backend.const api = (path: string, body?: object) =>  fetch("https://api.bundle.social/api/v1" + path, {    method: body ? "POST" : "GET",    headers: { "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY!, "Content-Type": "application/json" },    body: body ? JSON.stringify(body) : undefined,  }).then((res) => res.json());// 1. A customer signs up: create a team for their workspace and store team.id.const team = await api("/team", { name: "Acme Bakery" });await saveWorkspace(workspace.id, { bundleTeamId: team.id });// 2. "Connect accounts" button: send the customer to the hosted connect page.const { url } = await api("/social-account/create-portal-link", {  teamId: team.id,  socialAccountTypes: ["INSTAGRAM", "LINKEDIN", "FACEBOOK"],  redirectUrl: "https://app.example.com/settings/social",  logoUrl: "https://app.example.com/logo.png",  hidePoweredBy: true,});// 3. Composer: import the image the customer picked.const upload = await api("/upload/from-url", {  teamId: team.id,  url: "https://cdn.example.com/spring-menu.jpg",});// 4. Schedule. referenceKey stores your own ID so you can find the post later.const post = await api("/post", {  teamId: team.id,  title: "Spring menu",  referenceKey: "composer_8812",  postDate: "2026-05-14T10:00:00.000Z",  status: "SCHEDULED",  socialAccountTypes: ["INSTAGRAM", "LINKEDIN"],  data: {    INSTAGRAM: { type: "POST", text: "The spring menu is here.", uploadIds: [upload.id] },    LINKEDIN: { text: "Our spring menu is live.", uploadIds: [upload.id] },  },});// 5. Webhook: post.published fires when the post ends as POSTED or ERROR.// Verify the x-signature header (HMAC-SHA256 of the raw body) before trusting the event.app.post("/webhooks/bundle", async (req, res) => {  const { type, data } = req.body;  if (type === "post.published") {    await updateComposerStatus(data.teamId, data.referenceKey, data.status, data.errors);  }  res.sendStatus(200);});

Supported content

  • Embedded posting
  • Customer OAuth
  • Status tracking
  • Dashboard fallback
  • Analytics

Honest limitations

  • Your SaaS still needs to model teams, permissions, and user access around exposed workflows.
  • Native platform permission review can affect which customers can connect which account types.
  • White-label UI details should be validated against the product experience you want to ship.
  • The Free plan is for testing: 3 teams, 20 posts a month and no analytics.

Developer-first infrastructure

Visible post status

Track scheduled, processing, posted, retrying, and error states per post.

Verbose errors

When native APIs fail, we return human-readable error messages and actionable recovery steps.

Flat pricing

No per-post counting. Predictable pricing for teams managing many users, workspaces, and connected accounts.

Same-day support

Direct access to the engineers building the API. We respond to technical issues the same day, sometimes the same hour.

Technical guides & documentation

Questions developers ask before building

Can this power an embedded social scheduler?

Yes. Your SaaS calls the API for account connection, media uploads, drafts, scheduled posts and status. Your own UI renders the calendar and composer.

Do my customers need bundle.social accounts?

No. Your backend calls the API with your organization API key, and the hosted connect page opens from a signed, expiring link, so customers never sign in to bundle.social.

How do I keep each customer's data separate?

Create one team per customer workspace and pass its teamId on every call. Accounts, posts and uploads belong to the team. A team holds one connected account per platform, so a customer with two Instagram profiles needs two teams.

Can support teams inspect failed posts?

Yes. Each post keeps its status and a per-platform error message, and the dashboard gives non-engineers a place to review them. After the cause is fixed, POST /api/v1/post/:id/retry publishes the post again.

How much does a social media API for SaaS cost on bundle.social?

Plans are priced per organization: Pro is $100 a month and Business $400 a month, or $90 and $360 a month billed yearly. Paid plans include unlimited teams and connected accounts, with 10,000 and 100,000 posts a month.

Keep comparing your options