10.36 | August 07, 2025
Enhanced by the following feature: Chargeable/Non-Chargeable Meal Plans.
Chargeable/Non-Chargeable Meal Plans (FEA98435)
When using the API to update content in the CRS set the “Available to any guest” attribute to False if you do not want the attribute enabled. Set the attribute to True when you want to enable the “Available to any guest” attribute.
When the attribute is not included in the request the “Available to any guest” flag will not be enabled.
<Services>
<Service MealPlanCode="14" Included="true" Removal="false" AvailableToAnyGuest="true">
</Services>
10.34 | October 13, 2024
Updated to support new functionality from the following enhancements: Tracking an External System User’s API transactions and Enhance APIs for additional Hotel Content and Time Zones.
Tracking an External System User’s API transactions (FEA92169)
The SynXis APIs have been enhanced so customers can now provide additional user metadata that will be tracked in SynXis CRS. This metadata will allow visibility into which users from the customer’s application (external system) initiated the API transactions to SynXis CRS.
A new optional parameter (ApplicationUserMetaData) is now supported in the HTTP headers for inbound requests to SynXis CRS, as well as in the header of the token request for use with REST APIs. The ApplicationUserMetaData parameter has a maximum size of 60 characters.
Enhance APIs for additional Hotel Content and Time Zones (FEA92756)
For customers who want to manage their hotel content using SynXis APIs, we have enhanced SOAP and REST APIs to include additional hotel content related to Property Email and Time Zone.
The following partial sample XML shows how the Property Email will be represented:
<OTA_HotelDescriptiveContentNotifRQ>
<HotelDescriptiveContents>
<HotelDescriptiveContent>
...
<ContactInfos>
<ContactInfo>
...
<Emails>
<Email EmailType="5">test@sabre.com</Email>
</Emails>
</ContactInfo>
</ContactInfos>
...
</HotelDescriptiveContent>
</HotelDescriptiveContents>
</OTA_HotelDescriptiveContentNotifRQ>
The following partial sample XML shows how the Time Zone will be represented:
<OTA_HotelDescriptiveContentNotifRQ>
<HotelDescriptiveContents>
<HotelDescriptiveContent>
...
<TPA_Extensions>
...
<TimeZone LocationID="AU-QLD"/>
</TPA_Extensions>
</HotelDescriptiveContent>
</HotelDescriptiveContents>
</OTA_HotelDescriptiveContentNotifRQ>
A list of Time Zones supported in SynXis CRS are available here.