Docs/Channels/Booking.com

Manage Booking.com Properties

List the Booking.com properties connected to your workspace, read the Booking.com connection for a listing, and get its rooms and rate plans. Each property is returned once, with the Repull listings mapped under it — see Properties & Listings for the model. To publish a listing to Booking.com, use POST /v1/listings/{id}/publish/booking.

GET/v1/channels/booking/properties

Scope

  • Only properties connected to your workspace are listed. Inactive listings are left out of listings; find them with GET /v1/listings?status=inactive.
  • A property whose rooms are not mapped yet is still listed, with mappingStatus: "unmapped" and an empty listings array. Finish the mapping with POST /v1/connect/booking/map-rooms.
  • One property carries many listings — one per mapped room. listings[].roomBookingId is the Booking.com room id an availability or rate write takes.
  • GET /v1/channels/booking/properties/{id} and /rooms take a Repull listing id, NOT a Booking.com hotel id, despite the path. The hotel-id surface is PUT /v1/channels/booking/availability. A listing with no Booking.com mapping in your workspace returns 404 not_found.
  • A listing published under several Booking.com properties: reads use the oldest and report the rest in otherHotelIds; writes return 409 ambiguous_booking_mapping. Add ?hotel_id= to name one.

When a property opens on Booking.com

Booking.com keeps a property it has just connected closed ("XML: Being built" or "XML: Ready to open") until it is opened. The rule: Repull opens a Booking.com property only while every listing mapped to it is active. A listing you are not ready to sell stays inactive, and its property is never opened, however often it is connected, mapped or synced. When it is ready, activate it with POST /v1/listings/status (or PATCH /v1/listings/{id}): Repull opens its property, provided Booking.com's own readiness check passes.

  • Activating reports the result. The activation response has bookingProperties: one entry per Booking.com property, with outcome opened, refused (Booking.com's reasons are in blockers, e.g. "Room 1554900501 does not have kitchen or kitchenette"), not_needed (already open, or closed by you), or listing_inactive (another listing on the same property is still inactive). Fix what Booking.com lists, then send active: true again to retry.
  • Open or close it yourself with POST /v1/channels/booking/properties/{id} (id is the Repull listing id): {"action": "open"} runs Booking.com's readiness check and opens the property only if it passes. On a property that is not ready nothing changes, and the answer is 422 booking_rejected with Booking.com's reasons in blockers, so it is always safe to ask. open also reopens a property you closed. {"action": "close", "reason": "RENOVATION"} closes it on Booking.com (reason defaults to PROPERTY_NOT_AVAILABLE).
  • An inactive listing cannot be opened: open answers 403 listing_inactive. Activate it instead, which opens it.
  • Deactivating a listing does not close a property that is already open on Booking.com. Use close for that, or unlist to stop it selling while it stays open.
  • A listing under several Booking.com properties: name the one you mean with hotelId in the body, as for unlist.
# Keep a listing that is not ready inactive: its property is never opened
curl -X POST https://api.repull.dev/v1/listings/status \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"listingIds": ["31402"], "active": false}'

# Ready? Activate it, and Repull opens its Booking.com property
curl -X POST https://api.repull.dev/v1/listings/status \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"listingIds": ["31402"], "active": true}'
# { "active": true, "updated": ["31402"], "unchanged": [],
#   "bookingProperties": [{ "hotelId": "15549005", "listingIds": ["31402"], "outcome": "opened",
#                           "bookingStatus": "XML: Ready to open", "blockers": [] }] }

# Or open it on demand. Not ready? Nothing changes and Booking.com says why:
curl -X POST https://api.repull.dev/v1/channels/booking/properties/31402 \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action": "open"}'
# 422 { "error": { "code": "booking_rejected",
#   "message": "Booking.com did not open property 15549005. Booking.com says: Room 1554900501 does not have kitchen or kitchenette. Nothing was changed.",
#   "blockers": ["Room 1554900501 does not have kitchen or kitchenette"], "hotel_id": "15549005", … } }

# Close it on Booking.com
curl -X POST https://api.repull.dev/v1/channels/booking/properties/31402 \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action": "close", "reason": "RENOVATION"}'

Example

# List connected Booking.com properties
curl https://api.repull.dev/v1/channels/booking/properties \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# Booking.com connection for listing 4118 (Repull listing id)
curl https://api.repull.dev/v1/channels/booking/properties/4118 \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# Rooms and rate plans — the roomId / rateId used by availability writes
curl https://api.repull.dev/v1/channels/booking/properties/4118/rooms \
  -H "Authorization: Bearer sk_live_YOUR_KEY"
AI