Booking.com Fixes Missing Reservation Confirmations and Opens Photo API to 360-Degree Uploads

If your property took a booking through Booking.com before 4 August and your system never received the confirmation, that was a Booking.com bug, and it has now been fixed.

The fix landed in Booking.com's 1 September connectivity release, the biweekly changelog that documents what changes in the APIs your channel manager or PMS uses to talk to the platform. Most operators never read it directly. Their provider does. But this release contains a reservations bug worth knowing about, because it explains a category of missing bookings that was easy to blame on the wrong system.

The reservations bug

Booking.com logged the issue as ACI-4670 and ACI-4700: reservation confirmation messages were not generated for reservations made before 4 August 2026, which meant the confirmation XML events were never sent to the connectivity provider. Booking.com says those reservations have now been repaired.

The practical read: if you or your provider spent August chasing bookings that appeared on the extranet but never landed in your own system, this is a plausible cause. It is worth asking your provider whether the recovered events have been processed on their side, because Booking.com fixing the source does not automatically mean the message got picked up downstream.

A second fix in the same release covers the Room and Rate Plan Management API. Valid roomrate creation requests sent through version 1.3 of POST /hotels/ota/OTA_HotelProductNotif were being rejected with the error "Defined policy code is not available for this hotel: 38", even though identical requests worked in version 1.0. Booking.com says v1.3 now applies the same policy validation as v1.0. Providers mid-migration to the newer version were the ones affected.

360-degree photos

The one genuinely new capability: the Photo API now accepts 360-degree panoramic photos.

Booking.com has not said where those images surface in search results or on the property page, and the changelog entry is one line long. For operators, the question to put to your provider is simply whether they plan to expose the upload path. A capability that only exists at the API level does nothing until the software you actually use supports it.

Sustainability wording changed

Booking.com has rewritten the suggested copy for the sustainability facility types it introduced in 2020, including entries such as plastic removal. If your website or booking engine displays those facility names pulled from Booking.com's content codes, the strings you are showing are now out of date.

This is small but the kind of thing that quietly goes stale. Booking.com points partners to its updated hotel amenities and facilities code list to check the current wording.

Also in the release

The developer portal search has been improved to return more relevant results across the API documentation. That is housekeeping, not a product change.

The two previous cycles were thinner. The 18 August release was bug fixes only, including three separate reservations issues covering missing confirmation messages, missing cancellation messages, and cancellation messages that were wrongly including RoomStay elements. The 4 August release introduced Request to Book 2.0, which changes when availability gets blocked, and added guest withdrawals so travellers can cancel a pending request before a host acts on it.

Booking.com publishes the changelog roughly every two weeks. The next entry is due around mid-September.