# Changelog A changelog records and lists notable changes to products or projects with links to the relevant documentation. This changelog also includes changes to the documentation. The logs are chronological, with the newest date on top. Every two weeks you can find an overview of: - **What is new?** Refers to new API products or features. - **What is going to change?** Refers to upcoming changes or updates to existing API products or features. - **What has changed?** Refers to minor changes or updates to existing API products or features. - **What was fixed?** Refers to bug fixes. ## 28 April 2026 Happy Spring! In this release cycle, we are excited to introduce you to the new version 1.3 of the `POST OTA_HotelProductNotif` endpoint. Additionally, we want to bring your attention to five bug fixes. ### What is new? * **[Room type and rate plan management API](/connectivity/docs/room-type-and-rate-plan-management/understanding-room-types-and-rate-plans) New version of the `OTA_HotelProductNotif` endpoint is now live!** Booking.com has released a new version 1.3 of the `POST OTA_HotelProductNotif` endpoint. To learn more and start using it, see the [blog about What’s new in OTA_HotelProductNotif v1.3?](https://connectivity.booking.com/s/blog/launching-ota-hotelproductnotif-v1-3-the-latest-in-our-api-modernisation-efforts-MCZZFCPZ3UJRBJDH5GR5CW5LEJOU?language=en_US). We plan to deprecate the old version 1.0 by 15th of May 2026, and sunset it on 1st of September 2026. For more information, see the [Migration guide](/connectivity/docs/migration-guides/migrating-to-new-versions#introducing-v13-of-post-ota_hotelproductnotif). ### What was fixed? * **[Facilities API](/connectivity/docs/content-api-modules/facilities-api/introduction-to-facilities-api) Error when deleting all bathrooms (ACI-4544)** The system now correctly returns valid responses when deleting all bathrooms again when using the Facilities API. * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Intermittent 503 errors (ACI-4549)** The system now correctly returns reservation retrieval responses again when using the Reservations API. * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Cancellation XML contained roomstay information (ACI-4554)** The system now correctly returns cancellation XML messages without roomstay information again when using the Reservation API. * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Missing confirmation XML messages (ACI-4569)** The system now correctly returns confirmation XML messages for reservations again when using the Reservations API. * **[Extranet Pages] Unable to activate or deactivate connectivity connection in the Connectivity Provider page (ACI-4580)** Extranet users can now correctly activate or deactivate the connectivity connections again from the Connectivity Provider page. ## 14 April 2026 In this release cycle, we don't have any major updates. However, we want to bring your attention to two bug fixes. Read on for more information. * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Incorrect roomrate price (ACI-4486 and ACI-4499)** The system now correctly returns the roomrate price information when using the Reservations API. ## 31 March 2026 In this release cycle, we don't have any major updates. However, we want to bring your attention to two bug fixes. Read on for more information. * **[Room type and rate plan management API](/connectivity/docs/room-type-and-rate-plan-management/understanding-room-types-and-rate-plans) Incorrect `room_name` (ACI-4494)** The system now correclty returns the `room_name` when using the `POST xml/roomrates` endpoint. * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Cancellation messages incorrectly shared as modifications (ACI-4500)** The system now correctly returns all cancellation messages again when using the Reservations API. ## 17 March 2026 In this release cycle, we don't have any major updates. However, we want to bring your attention to two bug fixes. Read on for more information. * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Missing Promotion ID (ACI-4480)** The system now correctly includes the promotion ID in reservation messages again. * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Missing reservation messages (ACI-4497)** The system now correctly returns all reservation messages again when using the Reservations API. ## 3 March 2026 In this release cycle, we don't have any major updates. However, we want to bring your attention to one bug fix. Read on for more information. ### What was fixed? * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Incorrect guest count details in `guest_counts` (ACI-4461)** The system now returns correct `guest_counts` details in reservation messages again. ## 17 February 2026 In this release cycle, we don't have any updates. We will come back next time with more information. ## 3 February 2026 In this release cycle, we don't have any major updates. However, we want to bring your attention to one bug fix. Read on for more information. * **[Property API](/connectivity/docs/property-api/property-api-introduction) Incorrect `Invalid postal code: 00000 in invoice_settings for country code: AE` error (ACI-4422)** The system no longer incorrectly returns an `Invalid postal code: 00000 in invoice_settings for country code: AE` error when using the `POST /property-api/properties/{property_id}/settings` endpoint. ## 20 January 2026 In this release cycle, we don't have any major updates. However, we want to bring your attention to a few bug fixes. Read on for more information. * **[Property API](/connectivity/docs/property-api/property-api-introduction) Incorrect `allowed_values:["OTHER"]` error (ACI-4435)** The system no longer incorrectly returns an `allowed_values:["OTHER"]` error when using the `POST /property-api/status` endpoint. * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Incorrect `Total@Amount` in `PriceDetails` node (ACI-4425)** The system now returns correct `Total@Amount` of `PriceDetails/HotelView` and `PriceDetails/GuestView` nodes in reservation messages again. * **[Contacts API] Incorrect 500 error (ACI-4405)** The system no longer returns internal server error when calling the `PUT /contacts-api/properties/{propertyID}/contacts` and `PUT /contacts-api/properties/{propertyID}/contacts` endpoints. ## 6 January 2026 Happy new year! In this release cycle, we are excited to introduce the new `Try it` feature in our API documentation, which helps you perform static API response testing. Additionally, we want to bring your attention to a few bug fixes. Read on for more information. ### What is new? * **[Documentation] Enabling static API response testing** The developer portal now supports testing static API responses using the existing OpenAPI specifications. Use the `Try it` button available on the OpenAPI specification pages to test API requests with custom parameters and payloads. For example, you can use the specifications from the [Property API](/connectivity/docs/openapispecs/property-details-api/property-details-api-specification), [Rooms API](/connectivity/docs/openapispecs/rooms-api/rooms-api-specification), [Contacts API](/connectivity/docs/openapispecs/contacts-api/contacts-api-specification), [Facilities API](/connectivity/docs/openapispecs/facilities-api/facilities-openspec-remote-sync) and [Charges API](/connectivity/docs/openapispecs/charges-api/charges-api-specification). This makes it easier to explore the API behavior, validate request and response bodies, and iterate on integrations without leaving the developer portal. To learn more about this feature and how to use it effectively, see [About Try it.](/connectivity/docs/openapispecs/property-details-api/property-details-api-specification/about-try-it) ### What was fixed? * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Incorrect guest count details in `guest_counts` (ACI-4412)** The system now returns correct `guest_counts` details in reservation messages again. * **[Property API](/connectivity/docs/property-api/property-api-introduction) Incorrect `Authorization error` error (ACI-4406)** The system no longer incorrectly returns an `Authorization error` error when using the `PATCH /property-api/properties` endpoint. * **[Reservations API](/connectivity/docs/reservations-api/reservations-overview) Missing credit card details after the guest updates their card (ACI-4395)** The system now correctly includes the updated credit card details in the modification messages again. * **[Room type and rate plan management API](/connectivity/docs/room-type-and-rate-plan-management/understanding-room-types-and-rate-plans) Incorrect `Success` response when creating a rate (ACI-4386)** The system now correctly creates the rateplan and returns a valid `ResponseRatePlanCode` when using the version 1.0 `OTA_HotelRatePlanNotif` endpoint. * **[Authentication](/connectivity/docs/authentication) Valid JWTs incorrectly rejected with 401 errors (ACI-4384)** The system now correctly validates JWT tokens.