Intercom webhook payload example (company.created)

Intercom · event: company.created · content type: application/json

This is a representative sample — fake IDs, real structure. To see a payload with your data, point the provider at a capture URL (button below).

See it live, not frozen

One click creates a free capture bin with this exact payload already in it — pretty-printed, headers inspectable, replayable to your own endpoint:

Then paste the bin's URL into Intercom's webhook settings to capture a real delivery. No signup.

Headers

content-type: application/json
user-agent: intercom-parrot-service-client/1.0
x-hub-signature: sha1=472da249b88a6558b423d057a5d932bc94dce1da
accept: application/json

Body

{
  "type": "notification_event",
  "topic": "company.created",
  "id": "notif_ccd8a4d0-f965-11e3-a367-c779cae3e1b3",
  "app_id": "a86dr8yl",
  "created_at": 1788084122,
  "delivery_attempts": 1,
  "first_sent_at": 1788084122,
  "data": {
    "item": {
      "type": "company",
      "id": "531ee472cce572a6ec000006",
      "name": "Acme Team Inc.",
      "company_id": "6",
      "remote_created_at": 1787990400,
      "created_at": 1788084120,
      "updated_at": 1788084120,
      "custom_attributes": {}
    }
  }
}

Things that bite people

This example's signature actually verifies — but it's HMAC-SHA1, not SHA-256: X-Hub-Signature is sha1= + a 40-char hex HMAC-SHA1 of the raw body, key = your app's client_secret (Developer Hub → your app → Basic Info). GitHub-style verifiers that expect sha256= fail on every delivery. Set scheme "Intercom" + the secret (here ic_client_secret_sample_9fKw2Rt) on a capture bin for live ✓/✗ badges, or use the signature debugger.
Weakest retry policy of any major provider: you get 5 seconds to respond; a failure is retried exactly once, one minute later, and that's it. Too many errors and Intercom drops all notifications from that subscription for 15 minutes. Treat any downtime as guaranteed event loss and reconcile from the REST API.
Two responses have special meanings: a 410 Gone makes Intercom disable the subscription entirely (no more notifications until you re-enable), and a 429 throttles delivery for 1 minute–2 hours — events delayed past 2 hours are dropped.
Every topic shares the notification_event envelope: switch on topic, read the object from data.item (its type field tells you the shape), and use delivery_attempts / first_sent_at to spot retries of an event you already processed — id is stable across the retry.
created_at here is epoch seconds (many providers use ISO 8601 or epoch ms — parsers hardcoded for one format misread the other by a factor of 1000).

Send it yourself

Reproduce this delivery against any endpoint (your handler, a bin, staging):

$ curl -X POST https://your-endpoint.example/hook \
  -H 'content-type: application/json' \
  -H 'user-agent: intercom-parrot-service-client/1.0' \
  -H 'x-hub-signature: sha1=472da249b88a6558b423d057a5d932bc94dce1da' \
  -H 'accept: application/json' \
 -d '{
  "type": "notification_event",
  "topic": "company.created",
  "id": "notif_ccd8a4d0-f965-11e3-a367-c779cae3e1b3",
  "app_id": "a86dr8yl",
  "created_at": 1788084122,
  "delivery_attempts": 1,
  "first_sent_at": 1788084122,
  "data": {
    "item": {
      "type": "company",
      "id": "531ee472cce572a6ec000006",
      "name": "Acme Team Inc.",
      "company_id": "6",
      "remote_created_at": 1787990400,
      "created_at": 1788084120,
      "updated_at": 1788084120,
      "custom_attributes": {}
    }
  }
}'

← All payload examples · Signature debugger · Docs