Skip to content

Getting started with webhooks

Webhooks allow Booking.com to send requests to your server in real-time. They enable you to:

  • Provide prices for journeys via the Search webhook
  • Receive booking notifications when bookings are created, amended, or cancelled
  • Receive incident notifications when incidents are raised or updated

Setup steps

  1. Register your webhook base URL — provide your endpoint and OAuth credentials
  2. Implement OAuth 2.0 — build a token endpoint so Booking.com can authenticate when calling you
  3. Self-enrol — enable the Booking and/or Incident webhooks (Search is active by default after registration)

Note

The Search webhook is activated upon registration. Booking and Incident webhooks require separate self-enrolment.

Authentication direction

Webhook authentication works in the opposite direction to the API:

  • API calls (you → Booking.com): You authenticate using Booking.com's OAuth credentials
  • Webhook calls (Booking.com → you): Booking.com authenticates using YOUR OAuth credentials

You must implement an OAuth 2.0 token endpoint on your server. See Webhook Authentication for details.

Available webhooks

Webhook Purpose Self-enrolment required?
Search Provide real-time pricing for journeys No (active after registration)
Booking Receive new booking, amendment, and cancellation notifications Yes
Incidents Receive incident notifications Yes

Further reading