New to the Booking.com API? How Booking.com connectivity works, and what it lets you do · How to get Booking.com API access in 2026
Booking.com Reservations
Pull new and modified Booking.com reservations, get one reservation's details, and acknowledge the ones you have processed. Responses are Booking.com's raw reservation payloads; for the unified shape use GET /v1/reservations?platform=booking.
GET
/v1/channels/booking/reservationsParameters
typestringnew (default, not yet acknowledged) | modified | details
hotel_idstringBooking.com property id (alias property_id). Filters new / modified; required with reservation_id for details.
reservation_idstringWith hotel_id, returns that reservation's details.
Scope
hotel_idmust be a property connected to your workspace; any other id returns404 not_found, the same as an id that does not exist.- Without
hotel_id,newandmodifiedcover only your workspace's own Booking.com properties, and return404 not_foundif it has none. - A
reservation_idthat belongs to another workspace returns404 not_found. - Acknowledge with
POSTand{"reservation_ids": [...]}once you have stored each reservation. If any id is not one of your workspace's Booking.com reservations, nothing is acknowledged and404 not_foundnames those ids.
Example
# New (unacknowledged) reservations
curl https://api.repull.dev/v1/channels/booking/reservations \
-H "Authorization: Bearer sk_live_YOUR_KEY"
# One reservation's details
curl "https://api.repull.dev/v1/channels/booking/reservations?type=details&hotel_id=1234567&reservation_id=4218850692" \
-H "Authorization: Bearer sk_live_YOUR_KEY"
# Acknowledge after storing them
curl -X POST https://api.repull.dev/v1/channels/booking/reservations \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"reservation_ids": ["4218850692"]}'AI