Events & Payloads

Event type names are dot-namespaced (resource.action), the same convention used by Stripe, GitHub, and Meta. Every event's JSON body carries an event field with this exact string.

Support matrix

Not every channel can emit every event — mostly because the underlying platform (WhatsApp, Telegram, Instagram, Messenger) simply doesn't expose it. The event picker in the dashboard greys out anything unsupported for your selected channel, so you can't accidentally subscribe to something that will never fire.

Event reference

The exact JSON shape of each event, per channel, is below.

Payload envelope

Every webhook request shares the same envelope:

Code
{
  "event": "message.received",
  "created_at": "2026-09-16T10:00:00Z",
  "data": { },
  "raw_payload": { }
}

event matches one of the event types exactly. data's shape depends on the event — it's identical across channels except for a few noted fields. raw_payload is optional and only appears when you've turned it on — see below.

Raw provider payload

Each webhook endpoint has an Include raw provider payload toggle (off by default, in the Add/Edit Webhook form). When it's on, every delivery for that endpoint gets a raw_payload field — a sibling of data, not nested inside it — carrying the payload Chatmo itself received from the channel for that event, close to as-is.

Use data for anything it already covers, which is almost everything: the text, the file of a media message (data.media.url, stored in Chatmo), location, shared contacts, templates and button replies all have their own normalized block on every channel. Reach for raw_payload only when you need a provider-specific field that data doesn't expose. See Raw payload per channel below.

:::warning It's the channel's shape, not Chatmo's raw_payload mirrors WhatsApp's / Telegram's / Meta's own webhook item for that event, field names and all. It is not normalized, not versioned by Chatmo, and can change whenever the provider changes their API — Chatmo doesn't guarantee its shape the way it does for data. Only turn this on if you're prepared to handle that, and treat it as channel-specific integration code, not a stable contract. :::

raw_payload is only ever present for events Chatmo received from a channel. Events Chatmo itself originates never have one, regardless of the toggle:

The remaining events (message.received, message.reaction.added/.removed, message.status.*, template.status_updated, call.status_updated) do get one, on every channel that supports that event in the first place — see the support matrix.

:::tip Try it with Test The Test button sends a realistic per-channel raw_payload too (when the toggle is on), built from the same shapes shown on this page — a good way to see the exact field names before you write any code. See Testing & Delivery Logs. :::

message.received

Code
{
  "event": "message.received",
  "created_at": "2026-09-16T10:00:01Z",
  "data": {
    "message_id": "3f9c9d2a-6b7e-4d1a-9c2b-1a2b3c4d5e6f",
    "conversation_id": "b6e2a2b0-9b21-4b6a-8b7a-9d3f6c1a2e10",
    "external_message_id": "wamid.HBgLNjI4MjE0MTAwMDA=",
    "type": "TEXT",
    "content": "Hi, is this product still available?",
    "timestamp": "2026-09-16T10:00:00Z",
    "sender": {
      "type": "CONTACT",
      "id": "8a1b2c3d-4e5f-6789-abcd-ef0123456789",
      "name": "Sarah Wijaya"
    },
    "contact": {
      "id": "8a1b2c3d-4e5f-6789-abcd-ef0123456789",
      "name": "Sarah Wijaya",
      "phone": "6281234567890"
    }
  }
}

message.received and message.sent share this exact data shape on every channel. A partner can handle both with one parser.

Fields

Fields marked "–" are left out entirely (not sent as null) when they don't apply, so check for the key before reading it. New optional fields can be added over time; ignore keys you don't recognise.

Content types

type reflects what was actually sent. Read content for the text, then the block for that type:

LOCATION and CONTACT arrive from WhatsApp Official, WhatsApp Unofficial and Telegram. Facebook and Instagram (Messenger Platform) have no location or contact-share message, so on those two channels a contact can send TEXT, IMAGE, VIDEO, AUDIO, DOCUMENT or STICKER. An inbound TEMPLATE comes from WhatsApp Unofficial, when another WhatsApp Business account sends your number a template or interactive message.

Type-specific blocks

media

Present for IMAGE, VIDEO, AUDIO, DOCUMENT and STICKER. Chatmo downloads every inbound file from the channel and stores a copy in its own storage, so media.url is a direct https://files.chatmo.io/... link on every channel. You don't need a provider access token, a bot token or a Graph API call to fetch it, and it doesn't expire like a provider CDN link.

Code
{
  "event": "message.received",
  "created_at": "2026-10-13T17:01:52Z",
  "data": {
    "message_id": "40387d23-c8da-4bfc-a517-9927defc10d9",
    "conversation_id": "e4151f70-8eaf-4ca5-9db5-d22aea8981d5",
    "external_message_id": "TLGM3A32B4316ACE63FE",
    "type": "IMAGE",
    "content": "Is this the one you have in stock?",
    "timestamp": "2026-10-13T17:01:51Z",
    "sender": { "type": "CONTACT", "id": "231e258a-fc0d-4617-8aef-3bb481f1ba89", "name": "Fahmi Tyastomo" },
    "contact": { "id": "231e258a-fc0d-4617-8aef-3bb481f1ba89", "name": "Fahmi Tyastomo" },
    "media": {
      "id": "6c0f3b1e-2a4d-4f7b-9e1c-8d2a5b7c9e01",
      "url": "https://files.chatmo.io/chat/2026/10/13/photo_8f2c1a.jpg",
      "file_name": "photo_8f2c1a.jpg",
      "mime_type": "image/jpeg",
      "file_size": 184233,
      "thumbnail_url": "https://files.chatmo.io/chat/2026/10/13/photo_8f2c1a_thumb.jpg",
      "caption": "Is this the one you have in stock?"
    }
  }
}

Only url is guaranteed. The other fields are filled when known. In the rare case Chatmo could not copy the file from the channel (a provider error at that moment), id is missing and url is either the provider's original link (Facebook / Instagram, short-lived) or the whole media block is left out. The provider's own reference is still in raw_payload if you have it turned on.

location

Present for LOCATION.

Code
"location": {
  "latitude": -6.1753924,
  "longitude": 106.8271528,
  "name": "Monas",
  "address": "Gambir, Central Jakarta, Jakarta",
  "static_map_url": "https://files.chatmo.io/maps/2026/10/13/-6.17539,106.82715.png"
}

latitude and longitude are always set. name and address come from the channel for a named place, otherwise Chatmo looks them up from the coordinates (best effort). static_map_url is a map preview image.

contacts

Present for CONTACT. Always an array, even for a single contact.

Code
"contacts": [
  {
    "name": "Budi Santoso",
    "phone": "+6281298765432",
    "vcard": "BEGIN:VCARD\nVERSION:3.0\nFN:Budi Santoso\nTEL;type=CELL:+6281298765432\nEND:VCARD"
  }
]

vcard is only included when the channel sent the raw vCard text (WhatsApp Unofficial).

template

Present for TEMPLATE messages (and a WhatsApp Unofficial interactive message such as a button or list message). The body text is in content; the rest of the template is here:

Code
{
  "event": "message.received",
  "created_at": "2026-10-13T09:15:02Z",
  "data": {
    "message_id": "5d7e9f1a-2b3c-4d5e-8f90-a1b2c3d4e5f6",
    "conversation_id": "b6e2a2b0-9b21-4b6a-8b7a-9d3f6c1a2e10",
    "external_message_id": "3EB0A1B2C3D4E5F60718",
    "type": "TEMPLATE",
    "content": "Hi Sarah, your order #INV-2291 has been shipped.",
    "timestamp": "2026-10-13T09:15:00Z",
    "sender": { "type": "CONTACT", "id": "8a1b2c3d-4e5f-6789-abcd-ef0123456789", "name": "Toko Sepatu" },
    "contact": { "id": "8a1b2c3d-4e5f-6789-abcd-ef0123456789", "name": "Toko Sepatu", "phone": "6281234567890" },
    "template": {
      "type": "template",
      "header_media_url": "https://files.chatmo.io/chat/2026/10/13/header_19ab.jpg",
      "components": [
        { "type": "HEADER", "format": "IMAGE", "media_url": "https://files.chatmo.io/chat/2026/10/13/header_19ab.jpg" },
        { "type": "FOOTER", "text": "Reply STOP to unsubscribe" },
        {
          "type": "BUTTONS",
          "buttons": [
            { "type": "URL", "text": "Track order", "url": "https://example.com/track/INV-2291" },
            { "type": "QUICK_REPLY", "text": "Contact seller" }
          ]
        }
      ]
    }
  }
}

button_reply

Present when the contact tapped a quick-reply button, an interactive button or a list row (WhatsApp Official and Unofficial). type is TEXT and content is the button label.

Code
"button_reply": {
  "type": "quick_reply",
  "text": "Yes, confirm my order",
  "payload": "CONFIRM_ORDER"
}

type is quick_reply (template button), button_reply (interactive button) or list_reply (list row, which also carries description). payload is the ID you set on the button.

reply_to

Present when the contact replied to (quoted) an earlier message.

Code
"reply_to": {
  "message_id": "7c1d2e3f-4a5b-6c7d-8e9f-0a1b2c3d4e5f",
  "external_message_id": "wamid.HBgLNjI4MjE0MTAwMDE="
}

message_id is set when the quoted message is known to Chatmo; external_message_id is the channel's ID for it.

referral

Present on the first message of a chat that started from a Click-to-WhatsApp ad or an Instagram ad / post.

Code
"referral": {
  "source_type": "ad",
  "source_id": "120208000000000001",
  "source_url": "https://fb.me/3abcDEF",
  "ctwa_clid": "ARAkLmN0pQrStUvWxYz",
  "headline": "Free shipping this week",
  "body": "Chat with us to order",
  "media_type": "image",
  "thumbnail_cdn_url": "https://files.chatmo.io/ctwa/2026/10/13/ad_120208.jpg"
}

call

Present for CALL_REQUEST and CALL_ENDED (WhatsApp Official calling): the call snapshot, for example call_id, direction, status and duration_seconds. See call.status_updated for live call status.

Raw payload per channel

Everything above is in data on every channel, so most integrations never need raw_payload. Turn it on only when you need a provider-specific field that data doesn't carry. For media, the raw payload holds the provider's own reference to the file, which works differently per channel:

Below is one raw_payload example per channel: a TEXT message (the simplest case) and an IMAGE message (to show the media reference). The other content types (VIDEO, DOCUMENT, LOCATION, CONTACT) follow the same object shape with a different nested field; the reference table under each channel lists their field names.

WhatsApp Official

Wrapped in Meta's full webhook envelope — object → entry → changes → value — exactly like Meta's own webhook reference, scoped down to the one message that triggered this delivery (entry/changes each have exactly one element).

Code
{
  "object": "whatsapp_business_account",
  "entry": [
    {
      "id": "102938475610293",
      "changes": [
        {
          "field": "messages",
          "value": {
            "messaging_product": "whatsapp",
            "metadata": {
              "display_phone_number": "15550000001",
              "phone_number_id": "106540000000001"
            },
            "contacts": [
              { "profile": { "name": "Sarah Wijaya" }, "wa_id": "6281234567890" }
            ],
            "messages": [
              {
                "from": "6281234567890",
                "id": "wamid.HBgLNjI4MjE0MTAwMDA=",
                "timestamp": "1757999999",
                "type": "text",
                "text": { "body": "Hi, is this product still available?" }
              }
            ]
          }
        }
      ]
    }
  ]
}

Code
{
  "object": "whatsapp_business_account",
  "entry": [
    {
      "id": "102938475610293",
      "changes": [
        {
          "field": "messages",
          "value": {
            "messaging_product": "whatsapp",
            "metadata": {
              "display_phone_number": "15550000001",
              "phone_number_id": "106540000000001"
            },
            "contacts": [
              { "profile": { "name": "Sarah Wijaya" }, "wa_id": "6281234567890" }
            ],
            "messages": [
              {
                "from": "6281234567890",
                "id": "wamid.HBgLNjI4MjE0MTAwMDE=",
                "timestamp": "1757999999",
                "type": "image",
                "image": {
                  "id": "1029384756102938",
                  "mime_type": "image/jpeg",
                  "sha256": "a1b2c3...",
                  "caption": "Is this the one you have in stock?",
                  "url": "https://lookaside.fbsbx.com/whatsapp_business/attachments/?mid=...&ext=...&hash=..."
                }
              }
            ]
          }
        }
      ]
    }
  ]
}

:::tip Chatmo reconstructs this, it doesn't forward Meta's original bytes Meta batches multiple messages/statuses into one webhook call (value.messages can have more than one entry). Chatmo already splits a batch into one delivery per message before this reaches your endpoint, so raw_payload rebuilds the same object/entry/changes/value structure Meta documents around just the one message — field-for-field accurate, but not a byte-identical copy of what Meta originally sent (a metadata field Meta included that Chatmo didn't store comes back empty rather than fabricated). :::

WhatsApp Unofficial

Code
{
  "event": "message.received",
  "device_id": "device-0f3a9c21",
  "partner_id": "partner-001",
  "timestamp": 1757999999,
  "data": {
    "chat": "[email protected]",
    "sender": "[email protected]",
    "message_id": "3EB0C767D26A1D4E5F6A",
    "sender_name": "Sarah Wijaya",
    "message_type": "TEXT",
    "text": "Hi, is this product still available?"
  }
}

Code
{
  "event": "message.received",
  "device_id": "device-0f3a9c21",
  "partner_id": "partner-001",
  "timestamp": 1757999999,
  "data": {
    "chat": "[email protected]",
    "sender": "[email protected]",
    "message_id": "3EB0C767D26A1D4E5F6B",
    "sender_name": "Sarah Wijaya",
    "message_type": "IMAGE",
    "caption": "Is this the one you have in stock?",
    "media_url": "https://files.chatmo.io/media/9c1a2b3d.jpg",
    "mimetype": "image/jpeg",
    "file_length": 184320
  }
}

Telegram

Code
{
  "update_id": 100000001,
  "message": {
    "message_id": 1001,
    "from": { "id": 123456789, "is_bot": false, "first_name": "Sarah", "last_name": "Wijaya" },
    "chat": { "id": 123456789, "type": "private" },
    "date": 1757999999,
    "text": "Hi, is this product still available?"
  }
}

Code
{
  "update_id": 100000002,
  "message": {
    "message_id": 1002,
    "from": { "id": 123456789, "is_bot": false, "first_name": "Sarah", "last_name": "Wijaya" },
    "chat": { "id": 123456789, "type": "private" },
    "date": 1757999999,
    "caption": "Is this the one you have in stock?",
    "photo": [
      { "file_id": "AgACAgEAAxkBTEST0001", "file_unique_id": "AQAD9BgA", "width": 1280, "height": 960, "file_size": 184320 }
    ]
  }
}

Facebook Messenger

Wrapped in Meta's documented Messenger Platform shape — object: "page" → entry[] → messaging[] — see Meta's Messenger webhook reference. entry/messaging each have exactly one element, same reasoning as WhatsApp Official above.

Code
{
  "object": "page",
  "entry": [
    {
      "id": "1000000000000002",
      "time": 1757999999000,
      "messaging": [
        {
          "sender": { "id": "1000000000000001" },
          "recipient": { "id": "1000000000000002" },
          "timestamp": 1757999999000,
          "message": {
            "mid": "m_AbCdEfGhIjKlMnOpQrSt",
            "text": "Hi, is this product still available?"
          }
        }
      ]
    }
  ]
}

Code
{
  "object": "page",
  "entry": [
    {
      "id": "1000000000000002",
      "time": 1757999999000,
      "messaging": [
        {
          "sender": { "id": "1000000000000001" },
          "recipient": { "id": "1000000000000002" },
          "timestamp": 1757999999000,
          "message": {
            "mid": "m_AbCdEfGhIjKlMnOpQrSu",
            "attachments": [
              { "type": "image", "payload": { "url": "https://scontent.xx.fbcdn.net/v/....jpg" } }
            ]
          }
        }
      ]
    }
  ]
}

No LOCATION or CONTACT message type — Messenger Platform doesn't send those as inbound messages.

Instagram

Same Messenger Platform contract as Facebook, field names are identical — but note the top-level body is a JSON array, not a bare object, per Meta's Instagram webhook reference:

Code
[
  {
    "object": "instagram",
    "entry": [
      {
        "id": "1790293746510294",
        "time": 1757999999000,
        "messaging": [
          {
            "sender": { "id": "1780293746510293" },
            "recipient": { "id": "1790293746510294" },
            "timestamp": 1757999999000,
            "message": {
              "mid": "aWdfZAG1YQVZAERQVzVBaEFURVN…",
              "text": "Hi, is this product still available?"
            }
          }
        ]
      }
    ]
  }
]

Code
[
  {
    "object": "instagram",
    "entry": [
      {
        "id": "1790293746510294",
        "time": 1757999999000,
        "messaging": [
          {
            "sender": { "id": "1780293746510293" },
            "recipient": { "id": "1790293746510294" },
            "timestamp": 1757999999000,
            "message": {
              "mid": "aWdfZAG1YQVZAERQVzVBaEZAURVOU…",
              "attachments": [
                { "type": "image", "payload": { "url": "https://scontent.cdninstagram.com/v/....jpg" } }
              ]
            }
          }
        ]
      }
    ]
  }
]

No LOCATION or CONTACT message type, same as Facebook.

message.sent

Code
{
  "event": "message.sent",
  "created_at": "2026-09-16T10:00:06Z",
  "data": {
    "message_id": "7c1d2e3f-4a5b-6c7d-8e9f-0a1b2c3d4e5f",
    "conversation_id": "b6e2a2b0-9b21-4b6a-8b7a-9d3f6c1a2e10",
    "external_message_id": "wamid.HBgLNjI4MjE0MTAwMDE=",
    "type": "DOCUMENT",
    "content": "Here is the price list you asked for.",
    "timestamp": "2026-09-16T10:00:05Z",
    "status": "sent",
    "sender": {
      "type": "AGENT",
      "id": "c4d5e6f7-8a9b-0c1d-2e3f-4a5b6c7d8e9f",
      "name": "Rina Agent"
    },
    "contact": {
      "id": "8a1b2c3d-4e5f-6789-abcd-ef0123456789",
      "name": "Sarah Wijaya",
      "phone": "6281234567890"
    },
    "media": {
      "id": "0b1c2d3e-4f5a-6b7c-8d9e-0f1a2b3c4d5e",
      "url": "https://files.chatmo.io/chat/2026/09/16/price-list-2026.pdf",
      "file_name": "price-list-2026.pdf",
      "mime_type": "application/pdf",
      "file_size": 248112,
      "caption": "Here is the price list you asked for."
    }
  }
}

Same data shape as message.received: the same fields and the same type-specific blocks (media, location, template, reply_to, ...). A template you send from Chatmo carries the full template block (name, language, category, components, variables). The differences:

message.sent only carries raw_payload for sent_via: "device" (the echo Chatmo received from WhatsApp). Every other send was made by Chatmo itself, so there is no provider payload. Internal notes (private messages) never trigger message.sent.

message.status.delivered / .read / .sent / .failed

Code
{
  "event": "message.status.delivered",
  "created_at": "2026-09-16T10:00:08Z",
  "data": {
    "message_id": "7c1d2e3f-4a5b-6c7d-8e9f-0a1b2c3d4e5f",
    "external_message_id": "wamid.HBgLNjI4MjE0MTAwMDE=",
    "conversation_id": "b6e2a2b0-9b21-4b6a-8b7a-9d3f6c1a2e10",
    "status": "delivered"
  }
}

status mirrors the event suffix (sent, delivered, read, failed). WhatsApp Official and WhatsApp Unofficial only.

Code
{
  "object": "whatsapp_business_account",
  "entry": [
    {
      "id": "102938475610293",
      "changes": [
        {
          "field": "messages",
          "value": {
            "messaging_product": "whatsapp",
            "metadata": { "phone_number_id": "106540000000001" },
            "statuses": [
              {
                "id": "wamid.HBgLNjI4MjE0MTAwMDE=",
                "status": "delivered",
                "timestamp": "1757999999",
                "recipient_id": "6281234567890"
              }
            ]
          }
        }
      ]
    }
  ]
}

Code
{
  "event": "message.delivered",
  "device_id": "device-0f3a9c21",
  "partner_id": "partner-001",
  "timestamp": 1757999999,
  "data": {
    "chat": "[email protected]",
    "sender": "[email protected]",
    "message_ids": ["3EB0C767D26A1D4E5F6A"]
  }
}

message.reaction.added / .removed

Code
{
  "event": "message.reaction.added",
  "created_at": "2026-09-16T10:01:00Z",
  "data": {
    "message_id": "3f9c9d2a-6b7e-4d1a-9c2b-1a2b3c4d5e6f",
    "conversation_id": "b6e2a2b0-9b21-4b6a-8b7a-9d3f6c1a2e10",
    "emoji": "👍",
    "reactor": {
      "id": "+6281234567890",
      "name": "Sarah Wijaya",
      "type": "CONTACT"
    }
  }
}

emoji is an empty string on message.reaction.removed. reactor.type is CONTACT, AGENT, or AI_AGENT. raw_payload is only present when the reactor is a contact — an agent's own reaction has no inbound provider payload to attach, same reasoning as message.sent.

Code
{
  "object": "whatsapp_business_account",
  "entry": [
    {
      "id": "102938475610293",
      "changes": [
        {
          "field": "messages",
          "value": {
            "messaging_product": "whatsapp",
            "metadata": {
              "display_phone_number": "15550000001",
              "phone_number_id": "106540000000001"
            },
            "contacts": [
              { "profile": { "name": "Sarah Wijaya" }, "wa_id": "6281234567890" }
            ],
            "messages": [
              {
                "from": "6281234567890",
                "id": "wamid.HBgLNjI4MjE0MTAwMDM=",
                "timestamp": "1757999999",
                "type": "reaction",
                "reaction": { "message_id": "wamid.HBgLNjI4MjE0MTAwMDA=", "emoji": "👍" }
              }
            ]
          }
        }
      ]
    }
  ]
}

Code
{
  "event": "message.reaction",
  "device_id": "device-0f3a9c21",
  "partner_id": "partner-001",
  "timestamp": 1757999999,
  "data": {
    "chat": "[email protected]",
    "sender": "[email protected]",
    "reaction_target_message_id": "3EB0C767D26A1D4E5F6A",
    "reaction_emoji": "👍"
  }
}

Code
{
  "chat": { "id": 123456789, "type": "private" },
  "message_id": 1001,
  "user": { "id": 123456789, "is_bot": false, "first_name": "Sarah", "last_name": "Wijaya" },
  "date": 1757999999,
  "old_reaction": [],
  "new_reaction": [{ "type": "emoji", "emoji": "👍" }]
}

Code
{
  "object": "page",
  "entry": [
    {
      "id": "1000000000000002",
      "time": 1757999999000,
      "messaging": [
        {
          "sender": { "id": "1000000000000001" },
          "recipient": { "id": "1000000000000002" },
          "timestamp": 1757999999000,
          "reaction": { "action": "react", "emoji": "👍", "reaction": "like", "mid": "m_AbCdEfGhIjKlMnOpQrSt" }
        }
      ]
    }
  ]
}

Code
[
  {
    "object": "instagram",
    "entry": [
      {
        "id": "1790293746510294",
        "time": 1757999999000,
        "messaging": [
          {
            "sender": { "id": "1780293746510293" },
            "recipient": { "id": "1790293746510294" },
            "timestamp": 1757999999000,
            "reaction": { "action": "react", "emoji": "👍", "reaction": "like", "mid": "aWdfTEST0001" }
          }
        ]
      }
    ]
  }
]

conversation.assigned

Code
{
  "event": "conversation.assigned",
  "created_at": "2026-09-16T10:02:00Z",
  "data": {
    "conversation_id": "b6e2a2b0-9b21-4b6a-8b7a-9d3f6c1a2e10",
    "assigned_to": {
      "type": "USER",
      "id": "c4d5e6f7-8a9b-0c1d-2e3f-4a5b6c7d8e9f"
    }
  }
}

assigned_to.type is USER or TEAM. This is a Chatmo-internal action — never carries a raw_payload.

conversation.resolved

Code
{
  "event": "conversation.resolved",
  "created_at": "2026-09-16T10:15:00Z",
  "data": {
    "conversation_id": "b6e2a2b0-9b21-4b6a-8b7a-9d3f6c1a2e10",
    "resolved_by": {
      "id": "c4d5e6f7-8a9b-0c1d-2e3f-4a5b6c7d8e9f"
    }
  }
}

resolved_by is omitted when the conversation was resolved automatically (AI or Workflow) rather than by a human agent. This is also a Chatmo-internal action — never carries a raw_payload.

template.status_updated

Code
{
  "event": "template.status_updated",
  "created_at": "2026-09-16T09:00:00Z",
  "data": {
    "template_name": "order_confirmation",
    "language": "en",
    "status": "APPROVED"
  }
}

WhatsApp Official only. status mirrors Meta's template review states (APPROVED, REJECTED, PAUSED, DISABLED, PENDING_DELETION, IN_APPEAL, PENDING).

Code
{
  "object": "whatsapp_business_account",
  "entry": [
    {
      "id": "102938475610293",
      "changes": [
        {
          "field": "message_template_status_update",
          "value": {
            "event": "APPROVED",
            "message_template_id": 1000000000000001,
            "message_template_name": "order_confirmation",
            "message_template_language": "en"
          }
        }
      ]
    }
  ]
}

call.status_updated

Code
{
  "event": "call.status_updated",
  "created_at": "2026-09-16T09:30:00Z",
  "data": {
    "call_id": "d5e6f7a8-9b0c-1d2e-3f4a-5b6c7d8e9f0a",
    "status": "MISSED"
  }
}

WhatsApp Official only. status is one of RINGING, IN_PROGRESS, COMPLETED, MISSED, NO_ANSWER, REJECTED, CANCELED, FAILED.

Code
{
  "object": "whatsapp_business_account",
  "entry": [
    {
      "id": "102938475610293",
      "changes": [
        {
          "field": "calls",
          "value": {
            "messaging_product": "whatsapp",
            "calls": [
              {
                "id": "wacid.TEST0001",
                "to": "6281234567890",
                "from": "6281111111111",
                "event": "terminate",
                "timestamp": "1757999999",
                "direction": "USER_INITIATED",
                "status": "MISSED"
              }
            ]
          }
        }
      ]
    }
  ]
}