> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/integrations/webhooks/payload-reference.md).

# Payload reference

The exact JSON body and HTTP headers dCal sends to a webhook for each event: booking.created (personal and team), booking.rescheduled, booking.cancelled, booking.confirmed and the ping test, with samp

Every webhook delivery is a `POST` with a small JSON body: the event name and a `data` object whose fields depend on the event. This page lists each event's body and the headers that travel with it. The values in the samples are made up.

No screenshots here: everything on this page happens on your server.

***

## Headers

| Header              | Example            | Meaning                                                                                                                                                                                                        |
| ------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `content-type`      | `application/json` | The body is always JSON.                                                                                                                                                                                       |
| `X-Slate-Event`     | `booking.created`  | The event name, the same as `event` in the body.                                                                                                                                                               |
| `X-Slate-Signature` | `sha256=5d2c…`     | `sha256=` followed by the lowercase hex HMAC-SHA256 of the raw body, made with the webhook's signing secret. See [Verify the signature](https://docs.dapta.ai/dcal/integrations/webhooks/verify-signature.md). |
| `X-Slate-Delivery`  | (an ID)            | The ID of this delivery. Every retry of the same event to your endpoint carries the same ID, so you can skip a delivery you already handled. The **Ping** test does not carry it.                              |

Header names are case-insensitive; most frameworks give them to you in lowercase. The headers carry no timestamp.

***

## The envelope

Every body has the same two keys:

```json
{
  "event": "booking.created",
  "data": {}
}
```

| Field   | Type   | Meaning                                                                                                       |
| ------- | ------ | ------------------------------------------------------------------------------------------------------------- |
| `event` | string | The event name: `booking.created`, `booking.rescheduled`, `booking.cancelled`, `booking.confirmed` or `ping`. |
| `data`  | object | The fields of that event, listed below.                                                                       |

Every booking event carries the booking's `uid`. It stays the same for the whole life of the booking, so use it to link a `booking.created` to the events that follow.

Every booking event (`booking.created`, `booking.rescheduled`, `booking.cancelled` and `booking.confirmed`) also carries `utm`, the booking's campaign, when the booking has one. It has the same shape on every event; see the `utm` row under `booking.created`. When the booking has no campaign, the key is left out.

***

## booking.created

Sent when a booking is made, whether it is confirmed or a request waiting for your OK.

```json
{
  "event": "booking.created",
  "data": {
    "uid": "3f9c2a1e-8b7d-4c6e-9a5f-1d2e3c4b5a60",
    "status": "accepted",
    "startUtc": "2026-11-03T15:00:00.000Z",
    "endUtc": "2026-11-03T15:30:00.000Z",
    "title": "Intro call",
    "utm": {
      "utm_source": "newsletter",
      "utm_medium": "email",
      "utm_campaign": "november-demo"
    }
  }
}
```

| Field      | Type   | Meaning                                                                                                                                                                                                                                                                                                                                                                                         |
| ---------- | ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `uid`      | string | The booking's ID.                                                                                                                                                                                                                                                                                                                                                                               |
| `status`   | string | `accepted` for a confirmed booking, `pending` for a request that waits for your OK. See [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md).                                                                                                                                                                                                                      |
| `startUtc` | string | Start time, ISO 8601 in UTC.                                                                                                                                                                                                                                                                                                                                                                    |
| `endUtc`   | string | End time, ISO 8601 in UTC.                                                                                                                                                                                                                                                                                                                                                                      |
| `title`    | string | The event's name when the booking was made.                                                                                                                                                                                                                                                                                                                                                     |
| `utm`      | object | Only when the booking came with campaign parameters: the `utm_source`, `utm_medium`, `utm_campaign`, `utm_term` and `utm_content` it was booked with, each one only when present. They come from the booking page's address or, on an embedded page, from the address of the page that frames it. Bookings you make from the dashboard, and those made with an API key or over MCP, carry none. |

### On a team event

A booking on a team event sends a shorter `data`: no `endUtc` and no `title`, and `utm` only when the booking came with campaign parameters. Team bookings are always confirmed.

```json
{
  "event": "booking.created",
  "data": {
    "uid": "8a1d4f7c-2e9b-4b3a-a6c5-0f1e2d3c4b5a",
    "status": "accepted",
    "startUtc": "2026-11-03T16:00:00.000Z"
  }
}
```

***

## booking.rescheduled

Sent when the guest moves the booking from the link in their email, or your system moves it with `PATCH /v1/machine/bookings/{uid}`. The `uid` does not change.

```json
{
  "event": "booking.rescheduled",
  "data": {
    "uid": "3f9c2a1e-8b7d-4c6e-9a5f-1d2e3c4b5a60",
    "startUtc": "2026-11-05T14:00:00.000Z",
    "endUtc": "2026-11-05T14:30:00.000Z"
  }
}
```

| Field      | Type   | Meaning                                                                       |
| ---------- | ------ | ----------------------------------------------------------------------------- |
| `uid`      | string | The booking's ID.                                                             |
| `startUtc` | string | The new start time, ISO 8601 in UTC.                                          |
| `endUtc`   | string | The new end time, ISO 8601 in UTC.                                            |
| `utm`      | object | Only when the booking has a campaign. The same shape as in `booking.created`. |

### Moved through the Cal.com-compatible API

A move made with `POST /v2/bookings/{uid}/reschedule` gives the booking a new `uid`. The message carries the new `uid` and the previous one, and no times: read them with `GET /v2/bookings/{uid}` if you need them. See [Cal.com-compatible API](https://docs.dapta.ai/dcal/developers/cal-com-compatible-api.md).

```json
{
  "event": "booking.rescheduled",
  "data": {
    "uid": "9b2e7c4a-1f3d-4e5a-8c6b-2d1e0f9a8b7c",
    "rescheduledFromUid": "3f9c2a1e-8b7d-4c6e-9a5f-1d2e3c4b5a60"
  }
}
```

| Field                | Type   | Meaning                                                                                                       |
| -------------------- | ------ | ------------------------------------------------------------------------------------------------------------- |
| `uid`                | string | The booking's new ID. Later events use this one.                                                              |
| `rescheduledFromUid` | string | The ID the booking had before the move.                                                                       |
| `utm`                | object | Only when the booking has a campaign, which it keeps across the move. The same shape as in `booking.created`. |

***

## booking.cancelled

Sent when the guest, a host or the API cancels a booking, and when a host declines a request.

```json
{
  "event": "booking.cancelled",
  "data": {
    "uid": "3f9c2a1e-8b7d-4c6e-9a5f-1d2e3c4b5a60",
    "reason": "Something came up, I will book another day."
  }
}
```

| Field    | Type           | Meaning                                                                                                                                                                                                                                                                        |
| -------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `uid`    | string         | The booking's ID.                                                                                                                                                                                                                                                              |
| `reason` | string or null | The reason the guest typed when cancelling, or the one your system sent through the API. An empty string `""` when the guest cancels without typing one. `null` when no reason was sent, which is always the case for cancellations and declines made from the dCal dashboard. |
| `utm`    | object         | Only when the booking has a campaign. The same shape as in `booking.created`.                                                                                                                                                                                                  |

***

## booking.confirmed

Sent when a host confirms a request. The **Add webhook** dialog does not offer this event, and API keys cannot create webhooks, so the webhooks you add in dCal do not receive it.

```json
{
  "event": "booking.confirmed",
  "data": {
    "uid": "3f9c2a1e-8b7d-4c6e-9a5f-1d2e3c4b5a60"
  }
}
```

| Field | Type   | Meaning                                                                       |
| ----- | ------ | ----------------------------------------------------------------------------- |
| `uid` | string | The booking's ID.                                                             |
| `utm` | object | Only when the booking has a campaign. The same shape as in `booking.created`. |

***

## ping

Sent only when you click **Ping** on a webhook's row. It is signed like a real delivery, so it is the easiest way to test your signature check.

```json
{
  "event": "ping",
  "data": {
    "ok": true
  }
}
```

***

## What the payload does not carry

* **Guest details.** There is no name, email, phone or answers in any event. To get them into your CRM without code, use [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md).
* **Who made the booking.** The payload does not say whether the guest, a host, a Dapta agent or the API made it.
* **A timestamp.** To skip repeats, use the `X-Slate-Delivery` header: it is the same on every retry of one delivery.

> **💡 Tip:** Your endpoint receives the events of every booking in the workspace. Keep the `uid` of the `booking.created` events you care about and match the later events on it.

## Related

* [Webhooks](https://docs.dapta.ai/dcal/integrations/webhooks.md): add a webhook and choose its events.
* [Verify the signature](https://docs.dapta.ai/dcal/integrations/webhooks/verify-signature.md): check `X-Slate-Signature` in Node.js or Python.
* [REST API](https://docs.dapta.ai/dcal/developers/rest-api.md): read a booking's current status.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dcal/integrations/webhooks/payload-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
