Skip to content

Webhook Registration

What does it do?

The Webhook Registration endpoint allows you to register your base URL and OAuth credentials with Booking.com. This is the first step to receiving webhooks.

Why use it?

Registration is a prerequisite for receiving any webhooks. It tells Booking.com:

  • Where to send webhook requests (your base URL)
  • How to authenticate with your server (your OAuth credentials)

Note

Registering your base URL activates the Search webhook only. For Booking and Incident webhooks, you must also self-enrol.

Timing & propagation

After registering or updating your configuration:

  • Your config is stored immediately
  • Search requests will start flowing to your endpoint within up to 1 hour as the system refreshes its configuration cache
  • If your OAuth token endpoint returns HTTP 401 (e.g. because old credentials are no longer valid), the system will reload your configuration from the latest registration and retry — this can result in faster propagation than the 1-hour cache window

Note

The immediate reload is only triggered when your OAuth token endpoint explicitly returns HTTP 401 Unauthorized. Other errors (timeouts, 500s, connection failures) will not trigger a config reload — the system will continue using the cached configuration until the 1-hour TTL expires.

Tip

If you need to verify your endpoint is working, use the Sandbox search validation to test immediately without waiting for the cache refresh.

Rate limiting

Warning

Registration changes are limited to 1 request per 10 minutes per supplier. If you exceed this limit, you will receive an HTTP 429 response. Plan your configuration changes accordingly.

Updating your base URL

To change your webhook base URL:

  1. Call DELETE to remove your existing registration
  2. Call POST to register your new endpoint (subject to the 10-minute rate limit)
  3. New searches will begin flowing within up to 1 hour

See the reference for the endpoint specification.

Further reading