Instagram webhook fields: the full list
For a professional account on Instagram Login, Meta's webhook fields table lists comments, live_comments, messages, message_echoes, message_reactions, messaging_postbacks, messaging_referral, messaging_seen, messaging_optins, messaging_handover and standby, with mentions delivered inside comments; its examples add message_edit. Each needs instagram_business_basic plus instagram_business_manage_comments or, for most messaging fields, instagram_business_manage_messages. story_insights is not offered with Instagram Login.
easyCoexistence subscribes each connected Instagram account to comments, messages and mentions, and forwards those events to your HTTPS endpoint as they arrive, signed with that account's secret.
Fields a new Instagram product in the App Dashboard starts subscribed to, comments, messages and message_reactions among them.
Fields are selected for the app, not per account: an account receives the fields the app selected.
Access level Meta's setup guide lists for Instagram Login webhooks, and requires for comments and live_comments notifications.
Marked unavailable for Instagram Login in Meta's fields table, which offers it with Facebook Login and Unified Login.
When Meta introduced the message_edit webhook for Business Login for Instagram and Facebook Login for Business.
Which webhook fields does Instagram Login offer?
These, from Meta's fields table, with what fires each one taken from its examples and webhook reference. Each field also needs instagram_business_basic on top of the permission shown, and Meta requires Advanced Access for comments and live_comments notifications.
Which fields are not available with Instagram Login?
Three rows of Meta's fields table carry no Instagram Login permission, so an app on Instagram Login does not receive them, and one more field exists only outside it:
story_insights: a Story's metrics when it expires, with Facebook Login or Unified Login andinstagram_manage_insights. Meta's media insights reference says the insights webhook is not supported with Instagram Login.messaging_policy_enforcementandresponse_feedback: only in the column for Meta's Instagram Messaging API.- mentions as a field of its own: Facebook Login and Unified Login list it, with
instagram_manage_comments, while Instagram Login folds mentions into comments.
How do you subscribe to fields?
In two places. In the App Dashboard, under the Instagram product's webhook settings, save the callback URL and verify token, which triggers Meta's verification request, then select the fields; a new Instagram product starts subscribed to eight of them. Then subscribe each account with POST /<IG_ID>/subscribed_apps on graph.instagram.com, with subscribed_fields set to the fields selected in the dashboard, separated by commas.
POST https://graph.instagram.com/<IG_ID>/subscribed_apps
?subscribed_fields=comments,messages,message_reactions
&access_token=<INSTAGRAM_USER_ACCESS_TOKEN>
{ "success": true }Can each account get different fields?
No. Meta's setup guide says fields cannot be selected for each app user's account: an account receives the fields selected for the app. subscribed_fields on the account's subscription is meant to list the dashboard's fields, so a handler should expect any field the app selected and decide by what each event holds, not by what it asked one account for.
How do you tell the fields apart in a notification?
By the shape of the entry. Comment fields arrive in a changes array, each change naming its field. Messaging fields arrive in a messaging array with no field name, and the key beside sender, recipient and timestamp tells them apart:
- changes[].field: comments or
live_comments, with the comment in value. - message: messages, including echoes of the account's own messages, which carry
is_echoset to true. - reaction:
message_reactions. postback:messaging_postbacks. read:messaging_seen.message_edit:message_edit. - referral beside sender:
messaging_referral. A referral inside message belongs to messages, from a new thread or a Click-to-Direct ad. pass_thread_control,take_thread_controlorrequest_thread_control:messaging_handover, as Meta's webhook reference lists them.
Which fields does easyCoexistence subscribe to?
comments, messages and mentions, the list each Instagram account is subscribed with when it connects. With Instagram Login the mentions come inside comments, so the subscription covers comments and DMs, with echoes, Story replies, Story mentions and attachments among the DMs. The other fields in the table are delivered by Meta to an app subscribed to them and are not part of a connection's subscription. Once an endpoint is set with set_social_webhook_destination or the Partner API, easyCoexistence checks Meta's signature, answers Meta at once and POSTs each entry for the account to it:
- platform and
external_id: instagram, and the account's Instagram ID, equal to entry.id. account_id: the connection's ID in easyCoexistence, the one the MCP tools take.- entry: Meta's entry for the account, unchanged. Meta's object field and its X-Hub-Signature-256 header are not passed on.
- X-EC-Signature: t=<unix>,v1=<hex>, an HMAC-SHA256 of the timestamp, a dot and the raw body, keyed with the account's own secret.
- Delivery: one attempt of up to 8 seconds, with no redirects followed, no copy kept and no retries.
Common mistakes
- Waiting for a mentions field with Instagram Login. Meta folds mentions into the comments notification, so a handler keyed on field mentions never runs.
- Assuming an account only gets the fields its own subscription named. Meta delivers the fields selected for the app, so branch on what each event holds.
- Treating message.referral and a top-level referral as one event. The first rides on messages; the second is messaging_referral, for an ig.me link opened in an existing conversation.
- Waiting for story_insights with Instagram Login. Meta marks it unavailable there, so read a Story's metrics from the insights endpoint while it is up.
Events are not stored by default; an account with an automation switched on keeps its DMs and comments for 7 days. Set the endpoint with set_social_webhook_destination from Claude or ChatGPT, or with the Partner API. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Does Instagram Login have a mentions webhook field?
Not a separate one. Meta includes mentions in the comments notification for Instagram Login; mentions is its own field with Facebook Login and Unified Login.
Is story_insights available with Instagram Login?
No. Meta's fields table marks it unavailable for Instagram Login, and its media insights reference says the insights webhook is not supported there.
Which permissions does the Instagram messages webhook need?
instagram_business_basic and instagram_business_manage_messages, with Advanced Access, which Meta's setup guide lists for Instagram Login webhooks.
When did Meta add the message_edit webhook for Instagram?
On 10 September 2025, for Business Login for Instagram and Facebook Login for Business. An edit arrives in the messaging array under a message_edit key.
Keep reading
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Verified on