Instagram DM API

Beta

Instagram DM API for creator, support, and lead conversations

Inbound Instagram message webhooks, conversation state, and compliant outbound replies through one API. Now in beta on the Pro and Business plans.

Instagram DM API for teams that need inbound message webhooks, private conversation state, quick replies, ice breakers, and compliant outbound replies.

Last updated: September 2026

Request beta access View API docs

BetaInstagram messagingPrivate conversations

Request beta access

Request Instagram DM API beta access if your team needs incoming DM webhooks, quick replies, ice breakers, or compliant replies for creator and brand conversations. It is included on the Pro and Business plans.

Official APIs500k+ connected accountsDirect engineer support

Instagram DMs are private conversations with entry points, rules, and context

Instagram messaging workflows often begin before a DM is sent: a comment, story interaction, ice breaker, quick reply, or support handoff can shape the conversation path.

An API workflow needs to respect Meta account requirements and reply windows while still giving product teams enough context to automate responsibly.

Creators, brands, and customer-support tools need to know whether a message came from a campaign, a post comment, a profile prompt, or a manual support path.

What bundle.social handles

Incoming Instagram DMs are stored as conversations with the thread context support, CRM, and automation products need.

Ice breakers, quick replies, comment-triggered private replies, and payload clicks are handled as different routes into one conversation.

Outbound replies are checked against permissions and the messaging window, so teams do not treat Instagram DMs like open email.

Instagram DMs are live in beta

Teams on the Pro and Business plans can run Instagram DM workflows for creator monetization, lead capture, customer support, community engagement, or AI-assisted replies.

Workflow

How it works

The Instagram DM flow keeps the entry point, thread, payload, and reply eligibility together so teams can build more reliable private messaging products.

Capture inbound Instagram intent

Receive supported DM events and keep sender, account, payload, and entry-point metadata.

Route the conversation

Send the thread to a support queue, AI workflow, CRM step, or automation flow based on the event context.

Reply with guardrails

Send replies only when the account, permission, and messaging context allow it.

Product architecture

Build social media workflows without rebuilding every platform

Instagram DM API for private creator, support and lead conversations

Instagram DMs are often the place where creator monetization, lead capture, support requests and community engagement move from public interaction to private conversation. A useful Instagram DM API needs to preserve the full context behind that shift. The message may start from a story reply, comment-triggered private path, quick reply, ice breaker or manual support handoff.

That is why an Instagram DM workflow should not be reduced to one generic outbound endpoint. Product teams need incoming DM webhooks, thread metadata, entry-point awareness and policy-aware reply checks. This is especially important for tools that support creators, brands, agencies and AI-assisted customer conversations.

bundle.social’s Instagram DM API is in beta on the Pro and Business plans. It sits next to the broader Social Media DM API, but focuses specifically on Instagram conversation capture, reply eligibility and payload-aware automation.

Instagram DM webhooks, quick replies and conversation state

For Instagram automation to work properly, teams need to know what happened before the message appeared in the inbox. Did the user click an ice breaker? Did a comment trigger a private path? Did a quick reply payload route the person into a support flow? These details matter because they change how the conversation should be stored, routed and answered.

An Instagram DM API should help products preserve sender context, connected account data, payload information and the original entry point. That allows SaaS platforms, social inboxes and AI agents to move a conversation into the right queue, CRM record or automation step without losing the source of intent.

If your product also works with public Instagram content, compare this messaging surface with the Instagram API and the Comment to DM API. Public comments and private DMs may connect inside one customer journey, but they require different data models.

Why Instagram DMs are not built for unrestricted outbound campaigns

Instagram private messaging has platform rules, review requirements and account-level limitations. That means an Instagram DM API should not be designed as a bulk cold-DM tool. Outbound replies need to stay tied to supported user-initiated context, account permissions and Meta messaging rules.

This matters for developers building AI reply assistants, support products and lead flows. The product should know whether a reply is allowed before attempting to send it. It should also preserve enough thread context for a human support agent or automation system to understand why the user entered the conversation.

For teams that need broader publishing, scheduling or media workflows alongside Instagram messaging, the Social Media API and Media Upload API are useful adjacent pages to connect from this section.

Implementation

How to get the Instagram DM API beta

The Instagram DM 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

Instagram DM API capabilities for private conversations

This page centers Instagram-specific conversation needs instead of repeating the broader social DM page.

Instagram conversation capture

Incoming Instagram DMs are stored as conversations with the thread context support, CRM, and automation products need.

Entry-point aware replies

Ice breakers, quick replies, comment-triggered private replies, and payload clicks are handled as different routes into one conversation.

Policy-aware send checks

Outbound replies are checked against permissions and the messaging window, so teams do not treat Instagram DMs like open email.

Platform specifics

Instagram DM workflows need more than a send message endpoint

Instagram messaging products usually need entry prompts, private replies, quick replies, policy windows, and conversation state to work together cleanly.

Entry points

Ice breakers and comment-triggered private replies are different entry paths into the same conversation workflow.

Reply windows

Outbound replies stay aware of Meta messaging rules instead of treating Instagram DMs like email.

Conversation context

The API exposes enough thread context for support, automation, and product analytics to stay aligned.

Supported surfaces

Instagram DMsIncoming DM webhooksOutbound messagesIce breakersQuick repliesConversation context

Beta limitations

Instagram DM access depends on Meta permissions, account type, review status, and messaging rules.
This page is separate from public Instagram comment import and moderation workflows, even when a comment starts the private path.
The workflow is not designed for unsolicited bulk DM campaigns.
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 Instagram DM 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.

How is this different from Instagram comments?

Instagram DMs are private conversation messages. Instagram comments are public post comments. A comment may start a private path, but the data model and reply rules are different.

Do I need to reconnect my Instagram account?

Accounts connected before the beta may need to reconnect so Meta grants messaging permissions. Messaging is then enabled per connected account.

Keep comparing your options

Request beta access

Instagram API

Explore existing Instagram publishing and account workflows.

Social Media DM API

See the broader DM layer.

Comment to DM API

Explore comment-triggered private replies.

Social Media Comments API

Review the current comments surface for comment import, moderation, and replies.