Instagram Webhooks
Updated: Sep 16, 2026
Copy for LLM
Instagram Webhooks send real-time notifications to your server when supported activity occurs for an Instagram professional account connected to your app. Depending on the fields your app subscribes to, notifications can describe comments, mentions, story insights, messages, and other activity.
Setup overview
Receiving notifications requires four steps:
- Create and verify an HTTPS callback endpoint on your server.
- Subscribe your Meta app to the Instagram webhook fields required by your integration.
- Enable notifications for each app user’s Instagram professional account.
- Test the callback, subscription, and payload handling together.
Follow Set up Instagram Webhooks for the complete workflow.
Previous setup links
The following sections moved to the Webhooks setup guide:
- Setup steps
- Requirements
- Limitations
- Create a callback endpoint
- Verification requests
- Event notifications
- Validate verification requests
- Validate payloads
- Enable subscriptions
- Test delivery
- Sample application
- Verify the sample application
- mTLS for Webhooks
- Configure mTLS
Choose instructions for your API setup
Webhook configuration differs by Instagram API setup. In particular, the API host, access token, account identifier, and available fields are not interchangeable.
| API setup | Webhook model |
|---|---|
Uses an Instagram User access token and graph.instagram.com. | |
Uses Facebook Login authorization and graph.facebook.com. Requires the Instagram professional account to be linked to a Facebook Page. |
Webhook fields
Field availability and required permissions depend on the API setup used by your app. See the Instagram webhook fields and permissions matrix.
Payloads and testing
Use Webhook notification examples to compare payloads for each authorization setup and test your parser against the event types used by your integration.
Your endpoint must validate notification signatures, return a successful HTTPS response promptly, and handle duplicate deliveries. Webhooks do not provide a historical notification store, so retain the event data required by your product.