Facebook Messenger API

Beta

Facebook Messenger API for Page conversations and payload-driven flows

Page message webhooks, conversation storage, persistent menus, and supported Messenger replies through one API. Now in beta on the Pro and Business plans.

Facebook Messenger API for teams that need Page message webhooks, conversation storage, Get Started payloads, persistent menus, and supported Messenger replies.

Last updated: September 2026

Request beta access View API docs

BetaFacebook PagesMessenger payloads

Request beta access

Request Facebook Messenger API beta access if your Page workflow needs message webhooks, Get Started payloads, persistent menus, postbacks, or conversation storage. It is included on the Pro and Business plans.

Official APIs500k+ connected accountsDirect engineer support

Messenger Page workflows combine chat, page settings, and postback payloads

A Facebook Page conversation can start from a message, Get Started action, button click, persistent menu selection, or comment follow-up, and each path carries different context.

Page-level settings, Messenger policies, webhook delivery, postback payloads, and team routing need to work together before a product can call it a dependable API workflow.

Teams usually need Messenger data connected to support queues, lead forms, CRM handoffs, and automation logs rather than an isolated chat endpoint.

What bundle.social handles

Messenger threads stay tied to connected Facebook Pages, teams, and downstream customer records.

Get Started, persistent menu, and button events are structured triggers for automation flows.

Outbound actions respect Page permissions, messaging windows, payload constraints, and review requirements.

Built around Facebook Pages, not profile messaging

The beta is for teams that need Messenger workflows tied to Pages, business accounts, support queues, and payload-driven automation.

Workflow

How it works

The Messenger workflow receives Page events, keeps postback context intact, then routes eligible replies or automation steps with clear logs.

Handle Page message events

Receive Messenger webhooks for connected Facebook Pages and keep the event that started the thread.

Interpret Messenger payloads

Map Get Started, button, and persistent menu payloads to the correct automation, support queue, or CRM step.

Reply from a controlled flow

Send supported replies only when the Page and platform rules allow the action.

Product architecture

Build social media workflows without rebuilding every platform

Facebook Messenger API for Page-based conversation workflows

A Facebook Messenger API for business products needs to focus on Page-owned conversations, not personal profile messaging. Many Messenger workflows start from a Page message, Get Started action, persistent menu, button click, postback payload or comment follow-up. Each entry path carries different context, and that context should stay connected to the conversation.

bundle.social’s Facebook Messenger API is in beta on the Pro and Business plans. It covers Page message webhooks, conversation storage, payload-driven routing and supported replies, and it is especially relevant for SaaS platforms, agencies, support products, CRM tools and automation systems that want to connect Messenger conversations to customer workflows.

For products that need both Instagram and Messenger messaging, the broader Social Media DM API frames the shared conversation layer, while this page explains Page-specific requirements.

Messenger payloads, postbacks and automation routing

Messenger workflows often depend on payloads. A Get Started event, persistent menu selection or button click can tell the product what the user wants before a human agent ever opens the thread. If those payloads are not stored and routed correctly, the automation becomes fragile and support teams lose important context.

A Messenger API should help interpret Page events, preserve postback data and connect the thread to the correct workspace, customer record or support queue. This allows teams to build cleaner flows for lead qualification, support triage, onboarding, account help and AI-assisted replies.

For teams already working with Facebook publishing, comments or automation, useful related surfaces include the Facebook API, Facebook Comments API and Facebook Auto Reply.

Messenger API for support queues, CRM handoffs and AI tools

The most practical Messenger API use cases are rarely isolated chat widgets. They usually connect to an operational workflow. A customer sends a Page message, the system captures the event, identifies the connected Page, stores the payload, routes the message and checks whether an outbound response is eligible.

This is important for support queues, agency client dashboards, CRM handoffs and AI reply tools. The system should make it clear which Page owns the thread, which team can see it, what triggered the conversation and what action is allowed next.

If a product needs private messages from both Meta surfaces, link users from this page to Instagram DM API and Social Media DM API so they can compare Page Messenger workflows with Instagram private messaging.

Implementation

How to get the Facebook Messenger API beta

The Facebook Messenger API is in beta. It runs on the public API and in the dashboard, and we enable it for each organization while the beta runs.

Pick a paid plan

DMs and automations are included on the Pro and Business plans, with monthly limits per connected account.

Request beta access

Send the form on this page or message us from the dashboard. We turn the beta on for your organization.

Opt in each account

Messaging is enabled per connected account. Accounts connected before the beta may need to reconnect to grant messaging permissions.

Capabilities

What the Messenger API beta covers

This page focuses on Page-owned Messenger conversations, configuration surfaces, and postback payloads instead of duplicating the Instagram DM story.

Page conversation storage

Messenger threads stay tied to connected Facebook Pages, teams, and downstream customer records.

Postback and menu payloads

Get Started, persistent menu, and button events are structured triggers for automation flows.

Messenger-safe replies

Outbound actions respect Page permissions, messaging windows, payload constraints, and review requirements.

Platform specifics

Messenger-specific surfaces for Page workflows

Facebook Messenger has account-level entry settings and payload-driven events that need to be treated differently from generic chat messages.

Get Started

The first Page Messenger interaction can carry a configured payload that starts a guided automation flow.

Persistent menu

Menu entries are profile settings first, then automation triggers when users select them in Messenger.

Postbacks

Button and menu clicks carry stable payloads so product teams can route the next action reliably.

Supported surfaces

Facebook Page MessengerGet Started payloadsPersistent menusPostback buttonsConversation storagePage replies

Beta limitations

Support targets Facebook Pages and Messenger, not personal Facebook profiles.
Messenger platform policies, messaging windows, review requirements, and Page permissions still control what can run.
Persistent menu and Get Started setup are Page-level configuration surfaces, not generic chat commands.
Beta access is included on the Pro and Business plans and turned on per organization. The Free plan does not include DMs or automations.
During the beta, conversations, messages, and automation run history are kept for 30 days.
Official platform rules still apply, including permissions, messaging windows, review requirements, and provider payload limits.

FAQ

Questions developers ask before building

Is Facebook Messenger API available in bundle.social today?

Yes, in beta. It is included on the Pro and Business plans, over the public API and in the dashboard. We turn the beta on for each organization by hand, so request access with the form on this page or message us from the dashboard.

Which plans include DMs and automations?

Pro includes 200 sent DMs and 200 automation runs per connected account each month, Business includes 1,000 and 1,000, and Enterprise limits are set per contract. Incoming messages do not count. The Free plan does not include DMs or automations.

What does beta mean for my integration?

Endpoints, payload shapes, limits, and supported surfaces can still change while the beta runs. During the beta, conversations, messages, and automation run history are kept for 30 days.

Do Meta messaging windows and permissions still apply?

Yes. Meta permissions, account eligibility, messaging windows, payload limits, and review requirements still apply. bundle.social is designed to make those workflows easier to manage, not bypass platform rules.

Does this work with personal Facebook profiles?

No. The Messenger API targets Facebook Pages, not personal Facebook profiles.

Why are Get Started and persistent menu included here?

They are Messenger entry surfaces that can shape the first automation step, so they are configured on the Page alongside Messenger conversations rather than as separate features.

Keep comparing your options

Request beta access

Facebook API

Explore existing Facebook Page publishing workflows.

Social Media DM API

See the broader DM layer.

Meta Automation API

Payload-driven automation.

Social Media Webhooks API

Connect future automation pages to event delivery, retries, and integration context.