Intercom Webhooks
Version 1.0.0
AsyncAPI description of Intercom's outbound webhook surface. Intercom delivers workspace events to a single subscriber URL configured per app under the Developer Hub > Webhooks settings. Each delivery is a single HTTP POST whose JSON body is a notification envelope of `type: notification_event`. The `topic` field on the envelope identifies the event class (for example `conversation.user.created`, `contact.user.updated`, `company.created`, `ping`). Source documentation: - Webhook models reference: https://developers.intercom.com/docs/references/2.13/webhooks/webhook-models - Webhook topics reference: https://developers.intercom.com/docs/references/2.13/webhooks/webhook-topics - Build a webhook integration: https://developers.intercom.com/docs/build-an-integration/learn-more/webhooks/ Security and signing: Intercom signs every outbound webhook request with the HMAC-SHA1 `X-Hub-Signature` header (RFC 2104). The signature is computed over the raw JSON request body using the Intercom app's `client_secret` as the shared key, and is delivered as the literal string `sha1=` followed by the 40-character hex-encoded digest. Subscribers should recompute the digest with constant-time comparison to verify authenticity. Intercom also sets `User-Agent: intercom-parrot-service-client/1.0`.
Channels
Messages
Servers
{webhookUrl}