Instagram comments webhook: the payload, field by field
Instagram's comments webhook field notifies an app when someone comments on, or replies to a comment on, a professional account's media, Reels included. Meta posts a change with field set to comments whose value carries the comment's id and text, the author's Instagram-scoped ID and username in from, the media's id and product type, and parent_id when the comment is a reply.
easyCoexistence subscribes each connected Instagram account to comments and forwards the comments events Meta delivers for it to your HTTPS endpoint as they arrive, signed with that account's secret and with no copy kept.
Present when the comment is a reply, holding the ID of the comment it replies to.
Added to from when the account comments on its own media, next to the account's own ID.
Separate field for comments during a Live broadcast; its notifications stop when the broadcast ends.
Required for comments and live_comments notifications; media owned by private accounts triggers none.
Time left to send a commenter one private reply, addressed by the comment's ID.
When does the comments field fire?
When someone comments on media the professional account owns, or mentions the account, once the app and the account are both subscribed to the field. Each comment is one change in the notification, and these cases share its shape:
- A new comment on a post, a Reel, a Story or an ad, with media.
media_product_typesaying which surface the media is on. - A reply under an existing comment, which carries
parent_idwith the ID of the comment it replies to. - A comment the account makes on its own media, its replies included: from.id is the account's own ID, and from adds
self_ig_scoped_id. - An @mention of the account: with Instagram Login, Meta includes mentions in the comments notification instead of a field of their own.
- A comment during a Live broadcast comes on a separate field,
live_comments, with the same value shape, and stops when the broadcast ends.
What does a comments notification look like?
A POST whose JSON has object set to instagram and an entry array. Each entry is one professional account: its ID, the time Meta sent the notification, and a changes array holding one change per comment. A reply on a Reel looks like this:
{
"object": "instagram",
"entry": [
{
"id": "<IG_ID>",
"time": 1793448000,
"changes": [
{
"field": "comments",
"value": {
"id": "<COMMENT_ID>",
"parent_id": "<PARENT_COMMENT_ID>",
"text": "<COMMENT_TEXT>",
"from": {
"id": "<INSTAGRAM_SCOPED_ID>",
"username": "<USERNAME>"
},
"media": {
"id": "<MEDIA_ID>",
"media_product_type": "REELS"
}
}
}
]
}
]
}What does each field mean?
The fields Meta's webhook reference lists for a comment, from the outside in:
- entry[].id: the professional account's ID, the
user_idthat /me returns for it. It tells you which account the comment belongs to. - entry[].time: when Meta sent the notification, as a Unix timestamp. It is not when the comment was written.
- changes[].field: comments, or
live_commentsfor a Live broadcast. Check it before reading value. - value.id: the comment's ID, the one to reply to in public or in private, hide or delete.
- value.text: the comment's text, included when the comment has text.
- value.from.id and value.from.username: the author's Instagram-scoped ID and username. value.from.
self_ig_scoped_idappears when the account itself wrote the comment. - value.media.id and value.media.
media_product_type: the media commented on and its surface; Meta's media reference names AD, FEED, STORY and REELS. - value.
parent_id: on a reply, the ID of the comment it replies to. A top-level comment has none. - value.media.
ad_id,ad_titleandoriginal_media_id: listed in the reference for comments made on an ad.
What does the comments field not report?
A few things a handler might expect are left out of the event or never sent, according to Meta's setup guide and references:
- Comments on media owned by a private account: Meta sends no comment or mention notifications for them.
- Album IDs: the event does not include them, and Meta says to look the album up with the comment ID.
- Ad IDs for media used in dynamic ads.
- The comment's creation time: GET /<
COMMENT_ID>?fields=timestamp returns it in ISO 8601. - Live comments after the broadcast ends, when notifications for live media stop.
- Story mentions, which Meta's mentions API does not support; they reach the account as DMs instead.
- Past events: Meta keeps no notification history to query, so store what you need as each one arrives.
What does the comments field need?
With Instagram Login, the permissions instagram_business_basic and instagram_business_manage_comments, and Advanced Access, which Meta requires for comments and live_comments notifications. The app has to be Live and subscribed to comments in the App Dashboard, and each account has to be subscribed through POST /<IG_ID>/subscribed_apps with comments among its subscribed_fields. Meta strongly recommends this webhook over polling for comments, since it spares the rate limit.
How do you reply to a comment from the event?
With the IDs it carries. POST /<COMMENT_ID>/replies with a message posts a public reply under the comment, using value.id. POST /<IG_ID>/messages with recipient.comment_id set to value.id sends the author one private reply, within 7 days of the comment, or while the broadcast lasts on a Live. from.id is an Instagram-scoped ID, but a DM sent straight to it fails until the person has messaged the account, so the private reply is how to reach them by DM.
How does easyCoexistence forward a comment?
As it arrives, once an endpoint is set for the account with set_social_webhook_destination from Claude or ChatGPT, or with PUT /channels/:id/webhook on the Partner API. easyCoexistence subscribes each connected account to the fields that carry its comments, mentions and DMs, checks Meta's signature on each delivery, answers Meta at once, and POSTs each entry for that account to your HTTPS URL inside an envelope:
- platform and
external_id: instagram, and the account's Instagram ID, equal to entry.id. account_id: the connection's ID in easyCoexistence, the onelist_social_accountsreturns and the MCP tools take.- entry: Meta's entry for the account, unchanged, so a batched delivery becomes one POST per entry. Meta's object field and X-Hub-Signature-256 are not passed on.
- Delivery: one attempt, waiting up to 8 seconds, with no redirects followed, to an HTTPS address that resolves to a public IP. No copy is kept and nothing is retried.
POST <YOUR_ENDPOINT>
Content-Type: application/json
X-EC-Signature: t=1793448001,v1=<HEX_HMAC_SHA256>
{
"platform": "instagram",
"account_id": "<ACCOUNT_ID>",
"external_id": "<IG_ID>",
"entry": {
"id": "<IG_ID>",
"time": 1793448000,
"changes": [
{
"field": "comments",
"value": {
"id": "<COMMENT_ID>",
"text": "<COMMENT_TEXT>",
"from": { "id": "<INSTAGRAM_SCOPED_ID>", "username": "<USERNAME>" },
"media": { "id": "<MEDIA_ID>", "media_product_type": "FEED" }
}
}
]
}
}What do comment-to-DM rules do with the same event?
They read it alongside the forward. A rule matches when the comment contains one of its keywords, ignoring case, on one chosen post or on all of them, and sends the author the rule's DM as their private reply, plus a public reply if the rule has one. Comments by the account itself are skipped, automations that start on a comment take the ones no rule replied to, and a comment a rule replied to still reaches your endpoint. The rule's public reply can come back as a new comments event from the account itself.
Common mistakes
- Looking for comment_id. Under Instagram Login the comment's ID is in value.id; comment_id belongs to the payloads of Meta's other login setups.
- Replying to the account's own comments. Its replies come back as comments events with from.id equal to entry.id, and an automation that replies to them ends up talking to itself.
- Reading entry.time as the comment's time. It records when Meta sent the notification; the comment's own timestamp field says when it was written.
- Waiting for Live comments on the comments field. They arrive on live_comments, which needs its own subscription and goes quiet when the broadcast ends.
Comment-to-DM rules and automations reply to the same comments around the clock. 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 the Instagram comments webhook include replies to comments?
Yes. A reply arrives as its own comments event, with parent_id holding the ID of the comment it replies to.
Do Reels comments trigger the Instagram comments webhook?
Yes. A comment on a Reel comes on the comments field like one on a post, and media.media_product_type tells the two apart.
Why is my Instagram comments webhook not firing?
Most often the app is not Live or lacks Advanced Access, the account was never subscribed through /subscribed_apps, the media belongs to a private account, or the comment was on a Live, which uses live_comments.
Does the comments webhook include the commenter's username?
Yes. value.from carries the person's username next to their Instagram-scoped ID, so no extra call is needed to show who commented.
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