Schedule Post API

Social media scheduling API for posts, queues, and calendars

Plan, queue, and publish social media posts across connected accounts with scheduled dates, channel-specific fields, status tracking, and analytics.

Last updated: July 2026

API key authScheduled publishing14 platforms
Quick start
API request
1const response = await fetch("https://api.bundle.social/api/v1/post", {2  method: "POST",3  headers: {4    "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,5    "Content-Type": "application/json"6  },7  body: JSON.stringify({8    teamId: "team_123",9    title: "Launch update",10    postDate: "2026-05-12T09:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["TWITTER", "LINKEDIN", "INSTAGRAM"],13    data: {14      TWITTER: { text: "We just shipped a faster API workflow." },15      LINKEDIN: { text: "We just shipped a faster API workflow for social teams." },16      INSTAGRAM: { type: "POST", text: "New workflow is live.", uploadIds: ["upload_123"] }17    }18  })19});2021const post = await response.json();

Native scheduling

Most native social APIs do not give you one consistent scheduling model.
Scheduling alone is not enough when you also need media, retries, status, analytics, and client review.
Cross-platform calendars break down when every platform is a separate integration.

What bundle.social handles

Use one scheduled post workflow across supported social account types.
Keep dashboard review, API creation, media references, and post status in one place.
Use channel-specific payloads without forcing users to learn every native API.

Scheduling should work for developers and marketing teams

Developers get a clean API shape. Marketing teams get a calendar, drafts, media, and status they can understand without opening the docs.

Workflow

How it works

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

01

Create an API key

Generate an organization API key in the dashboard and use it with the x-api-key header.

02

Connect accounts

Connect each social account once. bundle.social keeps the account mapping ready for future posts.

03

Create or schedule posts

Send one request with the publish date, selected channels, and the fields each platform needs.

Product architecture

Build social media workflows without rebuilding every platform

Social media scheduling API for real product calendars

A social media scheduling API needs to do more than store a future date. Product teams need account connection, media upload references, platform-specific fields, draft states, approval steps, status tracking, and visibility when a scheduled post fails. Without those pieces, scheduling becomes a fragile timer wrapped around platform-specific publish calls.

bundle.social keeps scheduling inside the same workflow as post creation, media handling, and reporting. Your product can create a post for a future date, target connected accounts, pass native fields per platform, and let marketing teams review the same scheduled content in the dashboard. The API and calendar stay in sync instead of becoming two separate systems.

Scheduling across platforms without flattening every payload

Instagram Reels, TikTok videos, LinkedIn documents, Facebook Page posts, YouTube uploads, X posts, and Google Business Profile updates do not share one perfect shape. A scheduling API has to support one workflow while still allowing each platform to receive the data it actually needs.

That is why bundle.social uses a consistent post lifecycle with platform-specific data blocks. Your backend can schedule many channels through one API request or loop, while each channel keeps the fields that matter: upload IDs, privacy settings, captions, links, location context, thumbnails, or document metadata. Unification reduces integration work without hiding native constraints.

From scheduled posts to status, retries, and reporting

The value of scheduling is not only that content goes out later. It is that teams can plan campaigns, review drafts, attach assets, approve work, monitor status, and understand outcomes after publishing. A post should remain visible as it moves from draft to scheduled to processing to posted or failed.

With bundle.social, scheduled posts are tracked objects rather than invisible jobs. That gives SaaS platforms, agencies, internal tools, and AI workflows a reliable foundation for calendars, queues, bulk imports, client approvals, webhooks, analytics, and support workflows around the publishing lifecycle.

Capabilities

Scheduling that works across every channel

One request sets the publish date, targets the right accounts, and respects every platform's native fields.

One request for all channels

Set a publish date once and let the payload route to Instagram, LinkedIn, TikTok, and every other account in one call.

Draft, queue, and schedule modes

Choose from immediate, queued, or time-specific publishing depending on your campaign plan and approval workflow.

Channel-specific field control

Each platform's data block accepts the fields that platform actually supports without forcing a lowest-common-denominator shape.

Post status dashboard

Track scheduled, processing, posted, retrying, and error states in the dashboard your marketing team already uses.

Media references via upload IDs

Attach images, videos, carousels, and documents using upload IDs so the media library becomes a shared asset store.

API and dashboard in sync

Posts created through the API appear in the same calendar your marketing team uses for planning and review.

Developer example

Schedule a post

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

TypeScript
API request
1const response = await fetch("https://api.bundle.social/api/v1/post", {2  method: "POST",3  headers: {4    "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,5    "Content-Type": "application/json"6  },7  body: JSON.stringify({8    teamId: "team_123",9    title: "Launch update",10    postDate: "2026-05-12T09:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["TWITTER", "LINKEDIN", "INSTAGRAM"],13    data: {14      TWITTER: { text: "We just shipped a faster API workflow." },15      LINKEDIN: { text: "We just shipped a faster API workflow for social teams." },16      INSTAGRAM: { type: "POST", text: "New workflow is live.", uploadIds: ["upload_123"] }17    }18  })19});2021const post = await response.json();

Supported content

Scheduled postsDraftsMedia postsVideosCarouselsClient calendarsPost history

Honest limitations

  • Some native platforms have special scheduling windows or account-specific restrictions.
  • Media should be uploaded before creating scheduled posts.
  • Platform-specific data is still required for channels with unique content models.

Guarantees

Developer-first infrastructure

2% error rate

We handle the platform edge cases, media processing, and rate limits so your requests succeed.

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. Test us c;

FAQ

Questions developers ask before building

Can I schedule posts through the API?

Yes. Create a post with status SCHEDULED and a future postDate.

Can I schedule to multiple platforms at once?

Yes. Include multiple socialAccountTypes and provide the relevant platform-specific data.

Does bundle.social include a dashboard?

Yes. Teams can use the dashboard while developers automate the same workflow through the API.

Can I use media in scheduled posts?

Yes. Upload media first, then reference upload IDs in platform payloads.

Can I track scheduled post status?

Yes. bundle.social exposes post states such as scheduled, processing, posted, retrying, and error in the post workflow.