Webhooks

Mozrest sends webhook notifications to your endpoint whenever a booking is updated or cancelled. This keeps your system in sync in real time without polling.

Setup

During onboarding, provide Mozrest with:

Your webhook endpoint URL — Mozrest sends POST requests to this URL.
Authentication method — Bearer Token, Basic Auth, or a custom header.

Event Types

Event	Description
`update`	Booking details changed (time, party size, area, status)
`canceled`	Booking was cancelled

Update

Triggered when booking details change — date, party size, area, or status.

{
  "entity": "booking",
  "entity_id": "60e5a3ed409541da3650bd90",
  "action": "update",
  "data": {
    "partySize": 4,
    "date": 1742043600,
    "areaId": "60e5a3ed409541da3650bd90"
  }
}

Status Update (e.g. No-Show)

{
  "entity": "booking",
  "entity_id": "60e5a3ed409541da3650bd90",
  "action": "update",
  "data": {
    "status": "no-show"
  }
}

Cancellation

Triggered when a booking is cancelled.

{
  "entity": "booking",
  "entity_id": "60e5a3ed409541da3650bd90",
  "action": "canceled"
}

Handling Webhooks

Respond with HTTP 2xx to acknowledge receipt.
Retries will occur on 4xx or 5xx responses.
Ensure your handler is idempotent — the same event may be delivered more than once.

Setup​

Event Types​

Update​

Status Update (e.g. No-Show)​

Cancellation​

Handling Webhooks​