> For the complete documentation index, see [llms.txt](https://support.whapi.cloud/help-desk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.whapi.cloud/help-desk/receiving/webhooks/incoming-webhooks-format/other/calls.md).

# Calls

You can find more details about all parameters and their types in [the WebHook documentation](https://app.swaggerhub.com/apis-docs/HELLO_137/Whapi-Cloud-WhatsApp-API/1.8.5#/WebhookPayload).

The calls array contains all calls that were sent to the webhook URL. Sent on event "`calls.post`". We mentioned more about the events here:[Detailed webhook settings](/help-desk/receiving/webhooks/detailed-webhook-settings.md#mode-setting)

```
{
  "calls": [
    {
      "id": "ED3D9B4864F90327F10D24BAEED6CFB9",
      "from": "919984351847@s.whatsapp.net",
      "chat_id": "919984351847@s.whatsapp.net",
      "status": "initiated",
      "timestamp": 1713792453000,
      "group_call": false,
      "video_call": false,
      "offline_call": false
    }
  ],
  "event": {
    "type": "calls",
    "event": "post"
  },
  "channel_id": "MANTIS-M72HC"
}
```

```
{
  "calls": [
    {
      "id": "ED3D9B4864F90327F10D24BAEED6CFB9",
      "from": "919984351847@s.whatsapp.net",
      "chat_id": "919984351847@s.whatsapp.net",
      "status": "ringing",
      "timestamp": 1713792454000,
      "group_call": false,
      "video_call": false,
      "offline_call": false
    }
  ],
  "event": {
    "type": "calls",
    "event": "post"
  },
  "channel_id": "MANTIS-M72HC"
}
```

```
{
  "calls": [
    {
      "id": "ED3D9B4864F90327F10D24BAEED6CFB9",
      "from": "919984351847@s.whatsapp.net",
      "chat_id": "919984351847@s.whatsapp.net",
      "status": "missed",
      "timestamp": 1713792461000,
      "group_call": false,
      "video_call": false,
      "offline_call": false
    }
  ],
  "event": {
    "type": "calls",
    "event": "post"
  },
  "channel_id": "MANTIS-M72HC"
}
```

answered the call:

```
{
  "calls": [
    {
      "id": "9A8D1BC9430628934B085167CC0AF026",
      "from": "919984351847@s.whatsapp.net",
      "chat_id": "61371989950@s.whatsapp.net",
      "status": "answered",
      "timestamp": 1713792568000,
      "group_call": false,
      "video_call": false,
      "offline_call": false
    }
  ],
  "event": {
    "type": "calls",
    "event": "post"
  },
  "channel_id": "MANTIS-M72HC"
}
```

video call:

```
{
  "calls": [
    {
      "id": "5FC111DE89BCE0BD3401A2718382B314",
      "from": "919984351847@s.whatsapp.net",
      "chat_id": "919984351847@s.whatsapp.net",
      "status": "ringing",
      "timestamp": 1713792526000,
      "group_call": false,
      "video_call": true,
      "offline_call": false
    }
  ],
  "event": {
    "type": "calls",
    "event": "post"
  },
  "channel_id": "MANTIS-M72HC"
}
```

**Can I find out call duration via webhooks?**

No — this is not currently possible. WhatsApp does not send a call-end event, so there is no way to determine when a call finished or how long it lasted.

The calls webhook (`calls.post`) only fires for these status changes: `initiated`, `ringing`, `missed`, and `answered`. A termination event does not exist in the WhatsApp API, and therefore call duration cannot be calculated.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.whapi.cloud/help-desk/receiving/webhooks/incoming-webhooks-format/other/calls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.