Social media DM API for future cross-platform inbox products
Social media DM API waitlist for teams planning private messaging workflows across Instagram, Facebook Messenger, and future supported social channels.
Last updated: May 2026
Join the waitlist
Join the social media DM API waitlist if your future product depends on private social conversations, message webhooks, conversation storage, or policy-aware replies. Tell us which inbox or AI workflow you are building.
A useful social DM API needs conversation state, not just send-message access
What bundle.social is building
Designed for products that need a messaging layer
This page is for future clients building social inboxes, CRM handoffs, AI reply tools, creator platforms, or support workflows that need private social conversations inside their own product.
Workflow
Workflow shape
The planned DM workflow starts with inbound events, stores provider-specific thread context, then enables eligible replies and automation branches.
Receive DM webhooks
Capture supported private message events and make them available to product workflows that need thread-level context.
Attach conversation metadata
Store account, provider, sender, payload, and timestamp context so teams can route messages accurately.
Respond when eligible
Support outbound replies only when platform permissions, account type, and messaging windows allow the action.
Implementation
Current status for social media DM API
The social media DM 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.
social media DM API waitlist
Visitors should join the waitlist instead of expecting immediate public endpoint access for instagram dms, facebook messenger, and conversation storage.
Receive DM webhooks
Capture supported private message events and make them available to product workflows that need thread-level context.
Attach conversation metadata
Store account, provider, sender, payload, and timestamp context so teams can route messages accurately.
Capabilities
What the future social media DM API is meant to solve
The waitlist is focused on conversation ownership, event reliability, and reply eligibility rather than generic one-off message sending.
Shared conversation model
bundle.social is exploring a conversation layer that can keep supported DM threads tied to the correct social account, workspace, customer, and provider event.
Inbound-first messaging
The planned direction prioritizes real incoming messages and webhooks before outbound replies, so future sending is anchored to consent-sensitive platform rules.
Payload continuity
Quick replies, buttons, menu selections, and automation payloads should preserve the context that started the conversation.
Platform specifics
DM API rollout questions this page is meant to answer
Unified social messaging sounds simple until a real product needs private threads, webhook retries, provider payloads, and consent-sensitive reply windows in the same system.
Thread ownership
The future workflow needs to keep Instagram and Messenger conversations tied to the right connected account, team, customer workspace, and downstream integration.
Inbound before outbound
Message sending should be anchored around real incoming events, not unrestricted broadcast-style DM sending.
Payload continuity
Quick replies, buttons, and later automation steps should preserve the payload context that started the private conversation.
Supported surfaces
Current limitations
- This rollout starts with Meta messaging surfaces and does not promise every social network on day one.
- The product direction is not bulk cold-DM sending; outbound replies must stay tied to supported platform rules and user-initiated context.
- Rich messages, attachments, quick replies, and menus will remain provider-specific even when the conversation model is unified.
- Official platform rules still apply, including permissions, messaging windows, review requirements, and provider payload limits.
FAQ
Questions developers ask before building
Is social media DM API available in bundle.social today?
Not as public self-serve access yet. This early-access page collects interest from teams that need instagram dms, facebook messenger, conversation storage, and message webhooks and want to shape the private rollout.
Who should join this social media DM API waitlist?
Join if you are building a SaaS product, agency tool, AI agent, social inbox, or internal marketing workflow that needs instagram dms, facebook messenger, conversation storage, and message webhooks. Use the note field to explain what you need from receive dm webhooks.
How does this page relate to Social Media API and Social Media Webhooks API?
This page captures demand for social media DM 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.
Can this replace a social inbox?
The planned API is meant to power inboxes, AI agents, CRM handoffs, and support products. It is not presented as a finished hosted inbox replacement yet.
Will the DM API work outside Meta?
The waitlist is collecting broader social messaging demand, but planned support starts with Instagram and Facebook Messenger because those surfaces are closest to the current product direction.
Next pages
Keep comparing your options
Social Media API
Use the current public API for publishing and connected social account workflows.
Social Media Webhooks API
Connect future automation pages to event delivery, retries, and integration context.
Instagram DM API
Plan Instagram private messaging.
Facebook Messenger API
Plan Page Messenger workflows.