> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revreply.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Meeting Booked Webhook

> Sent when a lead successfully books a meeting.

<Badge color="blue">WEBHOOK</Badge> `POST`

<Note>
  This webhook is sent when a lead successfully books a meeting.
</Note>

## Overview

The `meeting.booked` webhook is triggered when a lead successfully books a meeting.

RevReply sends an HTTP `POST` request to your configured webhook URL containing an event object and information about the booked meeting.

## Event

The webhook event is identified by the following name:

```text theme={null}
meeting.booked
```

**Description:** A meeting has been booked.

## Payload

All webhook requests follow the same top-level structure, containing an `event` object and a `data` object.

### Event object

| Field         | Type      | Description                                                              | Example                       |
| ------------- | --------- | ------------------------------------------------------------------------ | ----------------------------- |
| `name`        | `string`  | Unique identifier of the webhook event.                                  | `meeting.booked`              |
| `description` | `string`  | Human-readable description of the event.                                 | `A meeting has been booked.`  |
| `sent_at`     | `string`  | ISO 8601 UTC timestamp indicating when the webhook was generated.        | `2026-07-17T20:30:15.000000Z` |
| `timestamp`   | `integer` | Unix timestamp, in seconds, representing when the webhook was generated. | `1784320215`                  |

### Data object

The `data` object contains information about the lead, conversation, and booked meeting.

| Field                | Type             | Description                                                       | Example                                     |
| -------------------- | ---------------- | ----------------------------------------------------------------- | ------------------------------------------- |
| `user_id`            | `integer`        | Identifier of the user.                                           | `123`                                       |
| `lead_id`            | `integer`        | Unique identifier of the lead.                                    | `98765`                                     |
| `inbox_manager_id`   | `integer`        | Identifier of the Inbox Manager associated with the conversation. | `12`                                        |
| `inbox_manager_name` | `string`         | Name of the Inbox Manager.                                        | `Sales Assistant`                           |
| `thread_id`          | `string`         | Unique identifier of the conversation thread.                     | `4e9bc3a2`                                  |
| `lead_name`          | `string`         | Name of the lead.                                                 | `Jane Doe`                                  |
| `phone_number`       | `string \| null` | Lead's phone number, when available.                              | `+15551234567`                              |
| `lead_email`         | `string`         | Primary email address of the lead.                                | `jane@example.com`                          |
| `lead_email_list`    | `array<string>`  | List of all known email addresses associated with the lead.       | `["jane@example.com"]`                      |
| `calendar_link`      | `string`         | URL of the booked calendar event or meeting.                      | `https://calendar.example.com/event/abc123` |

## Example payload

```json theme={null}
{
  "event": {
    "name": "meeting.booked",
    "description": "A meeting has been booked.",
    "sent_at": "2026-07-17T20:30:15.000000Z",
    "timestamp": 1784320215
  },
  "data": {
    "user_id": 123,
    "lead_id": 98765,
    "inbox_manager_id": 12,
    "inbox_manager_name": "Sales Assistant",
    "thread_id": "4e9bc3a2",
    "lead_name": "Jane Doe",
    "phone_number": "+15551234567",
    "lead_email": "jane@example.com",
    "lead_email_list": [
      "jane@example.com",
      "j.doe@company.com"
    ],
    "calendar_link": "https://calendar.example.com/event/abc123"
  }
}
```

## Handling the webhook

Your webhook endpoint should accept an HTTP `POST` request with a JSON body.

A successful webhook handler should process the event and return an appropriate HTTP success response.

Because webhook delivery is event-driven, your application should identify the event using `event.name` before processing the contents of `data`.

## Event details

| Property     | Value                               |
| ------------ | ----------------------------------- |
| Event        | `meeting.booked`                    |
| Method       | `POST`                              |
| Trigger      | A lead successfully books a meeting |
| Content type | `application/json`                  |