Glossary
Webhook
A webhook is a notification Meta sends to an app's server when something happens on a connected account, such as a new comment or message. Instagram webhooks are grouped into fields, for example comments, live_comments and messages, and an app only receives the fields it subscribed to. Meta recommends webhooks over repeated API calls because they lower the risk of hitting rate limits.
Fields a comment-to-DM tool uses
comments and live_comments need the instagram_business_basic and instagram_business_manage_comments permissions, and with Instagram Login mentions arrive inside the comments notification. messages covers DMs, story replies and story mentions, and messaging_postbacks reports button taps. Both need instagram_business_manage_messages.
Requirements
The app must be Live to receive notifications for its users, and the account that owns the media must be public, because private accounts do not receive comment or mention notifications. Meta signs every payload with a SHA256 signature in the X-Hub-Signature-256 header, which the server should check against the app secret before trusting the event.
Delivery and retries
If a delivery fails, Meta retries right away and then a few more times with decreasing frequency over 36 hours, after which the update is dropped. Notifications can come in batches of up to 1,000 updates, the same event can arrive twice, and Meta keeps no history, so the server has to store and deduplicate events itself. Elevion stores each event once by its ID and also checks recent posts for comments a notification may have missed.
For how this fits into the whole flow from comment to DM, read How comment-to-DM automation works.
Sources
- Meta for Developers: Instagram Webhooks
- Meta for Developers: Webhook fields and permissions
- Meta for Developers: Webhooks setup
- Meta for Developers: Webhook notification examples
Checked against Meta's documentation on 2026-10-20. Meta changes its rules from time to time, so its pages are the final word.