Facebook Messenger API for Page conversations and payload-driven flows
Facebook Messenger API for teams that need Page message webhooks, conversation storage, Get Started payloads, persistent menus, and supported Messenger replies.
Last updated: May 2026
Join the waitlist
Join the Facebook Messenger API waitlist if your Page workflow needs message webhooks, Get Started payloads, persistent menus, postbacks, or conversation storage.
Messenger Page workflows combine chat, page settings, and postback payloads
What bundle.social is building
Built around Facebook Pages, not profile messaging
This waitlist is for future clients that need Messenger workflows tied to Pages, business accounts, support queues, and payload-driven automation.
Workflow
Workflow shape
The planned 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 preserve 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.
Implementation
Current status for Facebook Messenger API
The Facebook Messenger API workflow is in progress or private beta direction. The page is live now so teams can join the waitlist while bundle.social prepares broader access.
Facebook Messenger API waitlist
Visitors should join the waitlist instead of expecting immediate public endpoint access for facebook page messenger, get started payloads, and persistent menus.
Handle Page message events
Receive Messenger webhooks for connected Facebook Pages and preserve 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.
Capabilities
Messenger API capabilities planned for bundle.social
This page focuses on Page-owned Messenger conversations, configuration surfaces, and postback payloads instead of duplicating the Instagram DM story.
Page conversation storage
The planned surface keeps Messenger threads tied to connected Facebook Pages, workspaces, and downstream customer records.
Postback and menu payloads
Get Started, persistent menu, and button events can become structured triggers for future automation flows.
Messenger-safe replies
Outbound actions will need to respect Page permissions, messaging windows, payload constraints, and review requirements.
Platform specifics
Messenger-specific surfaces planned around 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 need stable payload handling so product teams can route the next action reliably.
Supported surfaces
Current limitations
- This planned 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 treated as Page-level configuration surfaces, not generic chat commands.
- 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?
Not as public self-serve access yet. This early-access page collects interest from teams that need facebook page messenger, get started payloads, persistent menus, and postback buttons and want to shape the private rollout.
Who should join this Facebook Messenger API waitlist?
Join if you are building a SaaS product, agency tool, AI agent, social inbox, or internal marketing workflow that needs facebook page messenger, get started payloads, persistent menus, and postback buttons. Use the note field to explain what you need from handle page message events.
How does this page relate to Facebook API and Social Media DM API?
This page captures demand for Facebook Messenger API while linking to related bundle.social surfaces that are already public or closer to the current product direction.
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 planned workflow targets Facebook Pages and Messenger, 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 belong inside the Page Messenger plan rather than separate thin pages.
Next pages