All new features and improvements will be documented here. You can also stay updated on new functionalities by subscribing to our monthly API Newsletter
Our APIs are designed to be backward compatible by default. If a breaking change is ever necessary, we will notify you at least 3 months in advance via the email address registered for our newsletter. If you would like notifications sent to additional addresses, please contact us directly or register the additional email addresses to our newsletter.
By ensuring backward compatibility, we commit not to modify any existing transactions, nodes, or properties in ways that could impact your current implementation. However, please note that new, unrelated nodes or properties may still be introduced—these will not affect current operations. For this reason, we strongly recommend avoiding overly restrictive validations of the associated WSDL
These unreleased features are subject to change and are intended for inclusion in a future release. Once they become available, we will notify you via the newsletter.
- JP Transfer, added new NO_COORDINATES_FOUND error code. Refer to the Exceptions section for further information in this regard.
- Data Management, added new JP_HOTELGROUP_INVALIDCODE, JP_HOTELGROUP_INVALIDNAME, JP_HOTELGROUP_DELETE, JP_HOTELGROUP_INVALIDHOTEL, JP_HOTELGROUP_INVALIDHOTELGROUP, JP_HOTELGROUP_INVALIDSUPPLIERCODE error codes. Refer to the Exceptions section for further information in this regard.
- Data Management, added new ExternalHotelGroup request.
- JP Hotel, added new RoomCategory node within the HotelContent response.
- JP Car, added new ShowDocuments node within the RentacarAvail request.
- JP Car, added new OptionalElements node within the RentacarAvail response.
- JP Car, added new Documents object, which has been implemented within the RentacarAvail, RentacarBookingRules and RentacarBooking responses.
- JP Car, added new Name node within the RentacarLocationDetail object.
- JP Insurance, added new Price node within the InsuranceAvail request.
- JP Transfer, added the possibility of searching availability by coordinates:
- JP Transfer, added new INVALID_COORDINATE and JP_SEARCH_COORDINATES error codes. Refer to the Exceptions section for further information in this regard.
- JP Transfer, added new OriginLatitude, OriginLongitude, DestinationLatitude and DestinationLongitude properties within the TransferAvail request.
- Export, added new Loyalty node within the getBookings response.
- Data Management, added new ReservationLocator node within the SpecialPriceBooking request.
- Data Management, added new Items node within the SpecialPriceBooking response.
- Data Management, added new JP_SPECIALPRICE_INVALIDLOCATOR and JP_SPECIALPRICE_INVALIDPAX error codes. Refer to the Exceptions section for further information in this regard.
- Extranet, added new Type property within the FreeNights node of the Offer object.
- As of the 11th of February, 2025, on our Hotels APIs it is no longer be possible to perform destination-based availabilities, being instead mandatory to search availability by list of hotel codes (sending a maximum of 500 of them per request). This change will apply to the following APIs and transactions in specific:
- JP Hotel, on the HotelAvail request (on which the use of both @DestinationZone and @JPDCode will not be available).
- OTA Hotel, on the OTA_HotelAvail request (on which the use of @HotelCityCode will not be available).
- Export, added new creationDateFrom, creationDateTo, LastModifiedDateFrom, LastModifiedDateTo, LastModifiedTimeFrom, LastModifiedTimeTo filters within the getFinalCustomerList request.
- Export, added new ModifyDate node within the getFinalCustomerList response.
- Extranet, added new CheckInDates node within the Offer object.
- Extranet, added the possibility of establishing multiple Board nodes within the Boards node of the Offer object.
Here in this section you will be able to find the system updates that occurred during approximately the last year.
For any previous system updates, kindly refer to our archive section:
Change Log Archive