The GB read-only pilot is available to provisioned connector API callers when the Booking.com guest transport is enabled. Contact ajar for connector credentials and an endpoint. A dashboard API key does not authenticate to the connector API.
POST an empty body to /v1/connections/booking/guest with Authorization: Bearer YOUR_CONNECTOR_TOKEN. Use the returned connection_ref in x-connection-ref for all three operations. No Booking.com account login is needed.
Call booking.place.predict and use an items[].place_ref in booking.hotel.search with future checkin and checkout dates. Choose filter_id values from the returned filter catalog. Use that response’s search_ref and an items[].property_ref in booking.hotel.get.
GET /v1/connections/booking/current recovers your current connection. POST an empty body to /v1/connections/booking/refresh with x-connection-ref to renew it, or to /v1/connections/booking/revoke to revoke it locally. Renewal returns a new reference and retires the previous connection; predict and search again.
Place and search references last 15 minutes and belong to the same caller and connection. The pilot returns the initial search page; hotel room availability uses the original dates, currency and guests. Provider credentials stay in the platform’s encrypted connection service.
Authentication guide