Facebook API

Facebook API for posting and scheduling without the Meta app review maze

A Facebook API that resolves Page tokens at publish time, so a changed Page role comes back as a reconnect message instead of a silent failure.

Ship Facebook Page publishing without maintaining your own Meta app, token flow, and publishing infrastructure.

Last updated: July 2026

See pricing

Free plan with full API access, or a 14-day trial of a paid plan with unlimited accounts.

Read the API docs

API key authScheduled publishing15 platforms
Quick start
API request
1await 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: "Facebook campaign",10    postDate: "2026-05-14T10:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["FACEBOOK"],13    data: {14      FACEBOOK: { text: "Scheduled from bundle.social." }15    }16  })17});
customers
10,000+
connected accounts
500k+
uptime
99.981%
platforms
15

Building directly on Facebook Graph API

Facebook Graph API work brings app review, page tokens, permissions, channel selection, and media handling.
Page posts, Reels, Stories, links, and native scheduling each ask for different fields.
Publishing alone is not enough when teams also need status, retries, analytics, and reports.

What bundle.social handles

Schedule Facebook content from the same post workflow you use for every other channel.
Handle links, media, Reels, Stories, and native schedule fields when the connected Page allows them.
Track Facebook publishing and analytics beside the rest of your social channels.

Facebook Page publishing without token firefighting

Page posts, Reels, Stories, links, and native scheduling all depend on Meta permissions and token health. bundle.social keeps that complexity behind a repeatable publishing workflow.

Facebook API pricing

One price per organization, not per connected account. Both paid plans include unlimited connected accounts, so the bill does not move when a customer adds another profile, and both start with a 14-day free trial.

Free

For trying out

$0forever

  • 3 social sets
  • 20 posts a month
  • Full API access
  • All 15 platforms

Pro

Most popular

For power users

$100per month

  • Unlimited connected accounts
  • 10,000 posts a month
  • Full API access
  • All 15 platforms

Business

For growing businesses

$400per month

  • Unlimited connected accounts
  • 100,000 posts a month
  • Full API access
  • All 15 platforms

Yearly billing brings Pro to $90 and Business to $360 a month. Enterprise is custom pricing, so tell us what you need.

Every quota that applies, from API request rates to per-platform daily posting caps and monthly post allowances, is written down in the rate limits reference. The full pricing page carries the rest.

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

We resolve Page tokens at publish time

Facebook publishing runs on a Page access token derived from the user token, and Page roles can change after connection. You send one request; bundle.social resolves the current Page token and tells you to reconnect only when the Page relationship is genuinely broken.

Product architecture

Build social media workflows without rebuilding every platform

Facebook API for Page publishing, Reels, Stories, and links

A Facebook API integration is still a Meta Graph API project under the hood. Page tokens, permissions, app review, content types, Reels, Stories, links, native scheduling fields, media handling, analytics, and token health all affect the production workflow. A product that only wraps one publish call usually discovers the rest through customer support tickets.

bundle.social gives Facebook Page publishing a cleaner API surface while keeping Meta-specific rules visible. Your product can schedule Facebook content, attach media, use content-type fields, track status, and connect reporting beside other channels without maintaining a separate Facebook-only publishing backend.

Facebook posting API and scheduling for Pages

Most teams reaching for a Facebook posting API want three things: publish to a Page without babysitting Graph API tokens, schedule posts ahead of time, and know precisely which post failed and why. The native route gives you the publish call and leaves the rest - token refresh, per-content-type fields, retry decisions - as homework.

bundle.social treats Facebook scheduling as part of the same post object used everywhere else: set a postDate, attach media or a link, add Facebook-specific fields where the Page allows them, and track status per post. Page tokens are resolved at publish time, so a lapsed role surfaces as a clear reconnect request instead of a mystery 400.

Facebook Page operations need token and permission visibility

Facebook Page access can change because of revoked permissions, expired tokens, role changes, Meta review requirements, or account-level restrictions. Those are operational issues, not just API errors. Teams need to know which account, page, post, and payload failed so they can help customers reconnect or fix the content.

By tying Facebook publishing to connected accounts, scheduled posts, status tracking, and dashboard visibility, bundle.social gives support and engineering teams the context they need. That is especially useful for agencies, SaaS platforms, and multi-location brands where many Facebook Pages may be managed from one product.

Facebook campaigns run with Instagram and Google Business

Facebook is rarely managed alone. The same campaign may include Instagram Reels, LinkedIn updates, TikTok clips, Google Business Profile posts, YouTube uploads, and Facebook Page content. Each platform needs its own fields, but teams still want one calendar and one reporting flow.

bundle.social keeps Facebook inside that cross-platform workflow. Your product can publish Page content, schedule campaigns, inspect failures, and connect analytics where permissions allow, while the broader social stack handles media uploads, post history, comments, and reporting around the same customer workspace.

Teams shipping Facebook publishing on bundle.social

I assessed three products: Ayrshare, OneAll, and Bundle Social. After taking the time to properly evaluate all three, Bundle came out on top - and this wasn't a cost decision.
Phil · US · July 2026
Unlimited profiles without per-account fees is a huge win if you're managing multiple clients or building on top of the API.
Tucker · US · March 2026
Their social media API is so easy to set up and their documentation is really thorough and mentions everything. Most reliable one I've used.
Charles · CA · March 2026
Bundle Social has been reliable, easy to integrate, and much more affordable than other social media APIs we tested. The documentation is clear, new features are added regularly, and the support team responds quickly with real solutions.
Kuben · PH · July 2026
Their API doc is clean and well written, and their reactivity / availability makes it the best customer service I've been given to interact with.
Julien · FR · July 2026
I have been using this program for almost a year, and I have not yet seen a time when somebody was not online within minutes. I don't know how they do it, but you get an actual human.
Iana · MY · April 2026

Published reviews on Trustpilot, quoted verbatim. Collected July 2026.

Capabilities

Facebook API workflows for Page-owned campaigns

Page tokens, content-type fields, media, native scheduling, status, and reporting context for Facebook publishing.

Facebook-specific payload fields

Control the fields that matter on Facebook: captions, media types, privacy settings, and more, using the same post endpoint as every other channel.

API key authentication

Use one bundle.social API key for server-to-server requests. Your users still connect social accounts once through the hosted OAuth flow; bundle.social handles token storage and refresh.

Scheduling built in

Set a postDate to schedule Facebook content in advance, or create drafts and queue posts through the dashboard.

Media library integration

Upload Facebook-compatible media once and reference the same upload ID across multiple posts or campaigns.

Post status and retry tracking

Track Facebook posts through scheduled, processing, posted, retrying, and error states from the API or the shared dashboard.

Cross-platform publishing

Add other channels to the same post payload when Facebook is part of a multi-platform campaign. No separate API calls needed.

Platform specifics

Facebook Graph API details for Page publishing

Facebook looks familiar to users, but Page publishing still depends on token health, permissions, and content-type rules.

Page tokens expire

Facebook Page access tokens commonly expire after about 60 days. bundle.social refreshes them where possible, but security changes, revoked permissions, or Meta-side failures can still require users to reconnect.

Reels have API-specific limits

Facebook Reels via API support videos from 3 seconds to 8 minutes and require at least 540x960 resolution.

Long text is possible

Page post text can reach 50,000 characters, links up to 2,048 characters, and media titles up to 255 characters.

Developer example

Schedule a Facebook 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
1await 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: "Facebook campaign",10    postDate: "2026-05-14T10:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["FACEBOOK"],13    data: {14      FACEBOOK: { text: "Scheduled from bundle.social." }15    }16  })17});

Supported content

Page postsReelsStoriesImagesVideosLinksNative scheduling

Honest limitations

  • Facebook permissions, page access, and app review remain controlled by Meta.
  • Native scheduling fields are Meta-specific and only apply to eligible Facebook content.

Guarantees

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.

Resources

Technical guides & documentation

Social Media API

See the broader API layer for publishing, scheduling, media, analytics, and comments.

API Reference: Facebook

Documentation for Facebook Graph API integration.

FAQ

Questions developers ask before building

Which token does Facebook Page publishing actually use?

A Page access token derived from the user token of whoever connected the account. It is not the user token itself, and it stops working when the underlying Page role changes. bundle.social resolves the current Page token at publish time and only asks for a reconnect when the Page relationship is genuinely broken.

How do we tell a permission problem from a bad payload?

By whether other Pages still work. A revoked role or lapsed permission affects one Page; a malformed payload or unsupported media affects every Page it is sent to. Collapsing both into a generic publish error is what makes Facebook integrations expensive to support.

Do Reels and Stories use the same publishing call as a Page post?

They are separate surfaces with separate media rules: up to 10 items for a Page post, exactly one video for a Reel, exactly one item for a Story. Validating per post type before upload avoids a class of failure that only appears at publish.

Does this replace Facebook Graph API?

No. bundle.social calls Facebook Graph API for you and absorbs the work around it: token storage and refresh, media handling, scheduling, status transitions, and turning platform errors into a cause and a next action.

Are Facebook analytics available through the API?

Yes, for the metrics the connected account and Facebook Graph API actually expose. Availability depends on account type and granted permissions, so treat analytics as best-effort and delivery status as guaranteed.

Next pages

Keep comparing your options

Facebook API errors

Troubleshoot Facebook publishing failures, permissions, media validation, rate limits, and retry decisions.

Social Media API

See the full posting API workflow.

Schedule Posts

Build a cross-platform publishing calendar.

Analytics API

Report on the channels that expose data.