Webhooks Overview

Webhooks push events from Way to your systems as they happen - a booking confirmed, cancelled, or rescheduled; a listing published; a review submitted - so you don’t have to poll the API.

How delivery works

When a subscribed event occurs, Way sends an HTTP POST to your configured URL:

{
  "event": "booking.completed",
  "payload": { ... }
}

event identifies the event type; payload’s shape depends on it - see the event catalog.
If you configured a secret, the request carries an X-Way-Signature header you should verify - see Verify signatures.
Your endpoint has 10 seconds to respond with a 2xx. Failures are retried - see Delivery and retries.
Webhooks are managed in the Way dashboard, not through the API - see Setup.

Events

Event	Fires when
`booking.completed`	A booking is confirmed
`booking.modified`	A booking’s details change
`booking.rescheduled`	A booking moves to a different session
`booking.cancelled`	A booking is fully or partially cancelled
`booking.refunded`	A booking is fully or partially refunded
`experience.published`	An experience is published
`listing.published`	A listing is published
`listing.unpublished`	A listing is unpublished
`review.completed`	A guest submits a review
`financialReport.updated`	Financial report rows change (booking completed, refunded, …)
`financialReportV2.updated`	Financial report rows change (v2 report format)

A typical integration

Set up a webhook in the dashboard pointing at your endpoint, with a secret.
Verify the signature on every delivery, respond 200 fast, and process asynchronously.
Use booking.* events to keep your systems in sync, fetching full records via the Bookings API when you need more than the payload carries.
Test locally by triggering real events on staging.

​How delivery works

​Events

​A typical integration

How delivery works

Events

A typical integration