A meeting was booked from the chat and confirmed by the calendar.

postWebhookmeeting.booked

Headers

webhook-idstring required
webhook-timestampstring required
webhook-signaturestring required

Payload

idstring required
object'event' required
type'lead.captured' | 'handoff.requested' | 'outcome.submitted' | 'personal_link.opened' | 'meeting.booked' | 'meeting.rescheduled' | 'meeting.canceled' | 'conversation.started' | 'conversation.completed' | 'experiment.started' | 'experiment.winner_found' | 'knowledge.source_failed' required
created_atstring date-time nullable required
api_versionstring required
dataobject required

object is the contact, conversation, meeting, outcome request, link visit, experiment or knowledge source as the REST API returns it. lead.captured, meeting events and outcome.submitted also carry conversation; personal_link.opened carries link and contact.

Example payload

{
  "id": "evt_2b8f0c1d6e4a9937"
}

Response

Answer 2xx within 10 seconds; anything else is retried for three days.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.