Webhooks
Mozrest provides a webhook system that allows Booking Channels to receive real-time updates when relevant changes occur to a booking. This includes updates to the booking status, changes to the date/time, party size, or cancellations.
During onboarding, the partner must share the endpoint URL where Mozrest should send webhook notifications.
Supported authentication methods include Bearer Token, Basic Auth, or a custom header.
Event Types
Event | Description |
---|---|
update | Triggered when a booking is updated (e.g., time, party size, area, status) |
canceled | Triggered when a booking is cancelled |
Payload Example: Update
{
"entity": "booking",
"entity_id": "60e5a3ed409541da3650bd90",
"action": "update",
"data": {
"partySize": 4,
"date": "2021-11-06T12:00:00+02:00",
"areaId": "60e5a3ed409541da3650bd90"
}
}
Payload Example: No Show
{
"entity": "booking",
"entity_id": "60e5a3ed409541da3650bd90",
"action": "update",
"data": {
"status": "no-show"
}
}
Payload Example: Cancellation
{
"entity": "booking",
"entity_id": "60e5a3ed409541da3650bd90",
"action": "canceled"
}
Handling Webhook Events
- Respond with HTTP
2xx
to acknowledge receipt. - Retries may occur in case of
4xx
or5xx
responses. - Ensure idempotency on your side when processing repeated events.