Meta App Review

Meta App Review rejected? Ship Facebook and Instagram publishing without your own Meta app

bundle.social gives your product a managed, official publishing layer for Facebook Pages and Instagram Business accounts, including OAuth, token handling, scheduling, and platform maintenance. You keep building your product instead of operating social infrastructure.

Last updated: July 2026

View API docs

Official APIs. No per-account fees. Built for multi-tenant products.

Facebook PagesInstagram BusinessNo per-account fees
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: "customer_42",9    title: "Spring launch",10    postDate: "2026-08-03T10:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["FACEBOOK", "INSTAGRAM"],13    data: {14      FACEBOOK: { text: "The new collection is live.", uploadIds: ["upload_123"] },15      INSTAGRAM: { type: "POST", text: "The new collection is live.", uploadIds: ["upload_123"] }16    }17  })18});1920const post = await response.json();
Official Meta APIsFacebook Pages and Instagram Business accountsDirect engineer support

Running your own Meta app

App Review and permission requests stand between your code and the first customer who can connect a Page.
Reviewers ask for screencasts, a working test account, and flows your product does not have finished yet, then the queue restarts.
OAuth, long-lived tokens, Page token resolution, and refresh logic become a service you own forever.
Every Meta version bump, permission rename, and deprecation lands in your backlog instead of your roadmap.
Facebook and Instagram are two publishing models with different media rules, and you build both from scratch.

What bundle.social handles

Your users connect Facebook Pages and Instagram Business accounts through a maintained, already-reviewed integration.
Token storage, refresh, and Page token resolution at publish time happen on our side.
One endpoint publishes and schedules posts, images, video, Reels, and Stories where the surface supports them.
Per-post status and readable failure reasons instead of raw Graph API error codes.
Meta API changes are our maintenance work, not your sprint.

This page is about organic publishing, not Meta Ads or Meta Verified

bundle.social helps with organic Facebook Page and Instagram publishing. It does not resolve Business Manager verification, ad account restrictions, Meta Verified or the blue badge, or Meta Ads API access. If your rejection is about advertising or account verification, this is not the fix.

Workflow

How it works

Three steps, none of which involve registering a Meta developer app or waiting on a review queue.

01

Create an API key

Generate an organization API key in the dashboard and send it in the x-api-key header. There is no Meta developer account to register and no review to submit on your side.

02

Your users connect their accounts

Send customers through the hosted connection portal or your own branded flow. They authorize the Facebook Pages and Instagram Business accounts they already own, scoped to their team in your product.

03

Publish and schedule through one endpoint

Send one request per post with the fields each surface needs. Status, retries, and failure reasons come back per connected account.

Product architecture

Build social media workflows without rebuilding every platform

You do not need to run a Meta app to offer publishing in your product

Offering Facebook and Instagram publishing inside your own product normally means becoming a Meta app operator. You register a developer app, request publishing permissions, prepare a demo flow and screencast for App Review, respond to reviewer questions about features you have not shipped yet, and then keep that approval healthy as your product changes. The publishing code itself is rarely the hard part. The review cycle, the permission set, and the maintenance that follows are.

bundle.social removes that dependency. Your product calls one API, and your customers authorize their own Facebook Pages and Instagram Business accounts against an integration that is already reviewed and actively maintained. You are building a social product, not a token-refresh service, and App Review stops being a milestone on your roadmap.

Build and maintain it yourself, or use a maintained publishing layer

Building it yourself means App Review and permission requests, an OAuth and token lifecycle you own, publishing built from scratch per surface, and a maintenance stream that arrives whenever Meta changes something. Each new network your customers ask for repeats the whole exercise with a different set of rules.

Using bundle.social means a ready connection flow, managed tokens, one publishing API across Facebook, Instagram, and a dozen other networks, and integration maintenance handled on our side. The trade is deliberate: you give up owning the plumbing and keep owning the product, the UX, and the customer relationship.

Where this helps and where it does not

This helps when the blocker is publishing capability: your product needs to post to Facebook Pages and Instagram Business accounts on behalf of your customers, and your own Meta app is rejected, stalled in review, or missing the permissions you need. It also helps before you start, when you would rather not take on App Review as a product dependency at all.

It does not help when the blocker is your Meta account rather than your app. Business Manager verification, ad account restrictions, Meta Verified, and Meta Ads API access are separate processes that no publishing layer can resolve. Being clear about that up front saves everyone a sales call.

Scale

Built for products that serve many clients and many accounts

Multi-tenant publishing usually breaks on the commercial model before it breaks on the code. Per-account pricing turns every new client account into a cost decision.

No per-account fees

There is no cap on connected social accounts per workspace and no charge per connected Page or Instagram account. Pricing scales with posting volume instead.

Teams map to your customers

Each customer, brand, or client workspace gets its own team, keeping connected accounts, posts, media, and errors separated for support and debugging.

One integration, more than Meta

The same post endpoint reaches TikTok, LinkedIn, YouTube, X, Pinterest, Threads, and the rest, so the next platform your customers ask for is a payload change rather than another review queue.

Capabilities

What bundle.social handles

The Meta-specific work that sits between your product and a published post.

Facebook Page and Instagram Business connection

Users authorize the accounts they own. bundle.social maps each Page and its linked Instagram Business or Creator account to the team ID you send.

Managed OAuth

A hosted or embedded connection flow that already routes around the Meta-specific dead ends where non-technical users abandon halfway, like the business scope modal and the Instagram app deep link.

Token lifecycle

Long-lived tokens, refresh where Meta allows it, Page token resolution at publish time, and a clear reconnect signal only when the Page relationship is genuinely broken.

Publishing and scheduling

Immediate or scheduled posts with per-account payloads: text, links, images, video, Reels, and Stories where the surface supports them.

Post status tracking

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

Ongoing API maintenance

Graph API version bumps, permission renames, and endpoint changes are handled on our side while your integration keeps calling the same endpoint.

Scope

What stays with you

bundle.social is an infrastructure layer under your product. It does not take over the parts your customers pay you for.

Your product and UX

Your editor, calendar, approvals, and everything your customers actually look at stays yours.

Your customers

Accounts, billing, roles, and support live in your product. We never contact your users.

Your business logic

Content rules, workflows, and automation are yours. We publish what your product decides to send.

Your white-label experience

Connection flows and dashboards can carry your branding rather than ours.

Your own API layer

If your product exposes a public API, wrap bundle.social behind it. Your customers never need to know which infrastructure sits underneath.

Developer example

Publish to a Facebook Page and an Instagram account

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: "customer_42",9    title: "Spring launch",10    postDate: "2026-08-03T10:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["FACEBOOK", "INSTAGRAM"],13    data: {14      FACEBOOK: { text: "The new collection is live.", uploadIds: ["upload_123"] },15      INSTAGRAM: { type: "POST", text: "The new collection is live.", uploadIds: ["upload_123"] }16    }17  })18});1920const post = await response.json();

Supported content

Facebook Page postsFacebook ReelsFacebook StoriesInstagram feed postsInstagram carouselsInstagram ReelsInstagram StoriesScheduled posts

Honest limitations

  • Meta's platform rules still apply. bundle.social does not bypass App Review, permissions, or content policy. It changes who operates the reviewed app, not what Meta allows.
  • Users must connect a Facebook Page, and for Instagram a Business or Creator account. Personal Facebook profiles are not a publishable surface on the API.
  • Meta Ads API, Business Manager verification, ad account restrictions, and Meta Verified are out of scope.
  • Per-surface media rules still come from Meta: Reel length and resolution, Story format, and carousel item counts are validated before publish rather than waived.

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.

FAQ

Questions developers ask before building

Do I need my own Meta app?

No. Your users connect their Facebook Pages and Instagram Business accounts through bundle.social's integration. You never register a Meta developer app, submit App Review, or maintain publishing permissions yourself.

Does this bypass Meta's rules or App Review?

No, and treat anything that claims otherwise with suspicion. Publishing runs on the official Meta APIs with the required permissions under a reviewed app. What changes is who operates that app and keeps it approved: us instead of you. Meta's content policies, rate limits, and account requirements still apply to every post.

Can my users connect their own Facebook Pages and Instagram accounts?

Yes, and that is the normal setup. Each of your customers authorizes the accounts they own through a connection flow you can brand, scoped to their own team inside your product.

Does this support both Instagram and Facebook publishing?

Yes. Facebook Page posts, Reels, and Stories, plus Instagram feed posts, carousels, Reels, and Stories, each with the per-surface media rules Meta enforces validated before the post is sent.

Does bundle.social handle the Meta Ads API?

No. This is organic publishing only. Ad campaigns, ad accounts, Business Manager verification, and Meta Verified are outside what bundle.social does.

Can I use it in a multi-tenant or white-label SaaS?

Yes. Teams keep each customer's connected accounts, posts, media, and errors separated, and the connection flow and dashboards can carry your branding instead of ours.

Are there account limits?

No per-account fees and no cap on connected social accounts per workspace. Pricing scales with posting volume, not with how many Pages or Instagram accounts your customers connect, which is what makes agency and multi-tenant products workable.

What happens if Meta changes its API?

We update the integration. Graph API version bumps, permission renames, and endpoint changes are handled on our side, and your product keeps calling the same endpoint with the same payload shape.

Next pages

Stop maintaining social infrastructure. Start shipping your product.

Facebook API

Page posts, Reels, Stories, and native scheduling through one endpoint.

Instagram API

Feed posts, carousels, Reels, and Stories without running the container flow yourself.

Social Media OAuth API

See how your users connect accounts before you build the publishing side.

Social Media API for SaaS

Add publishing to your product without turning every network into a backend project.

Multi-Tenant Social Media API

Keep each customer's accounts, posts, and errors separated by team.

White-Label Social Media API

Ship connection flows and dashboards under your own brand.