10.34 | October 13, 2024
Updated to support new functionality from the following enhancement: Tracking an External System User’s API transactions.
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.
If ApplicationUserMetaData was provided in any reservation transactions via API, the value will be included in Cancel Reservation Notification response message as ResID_Type="3". The following partial XML sample shows how the metadata will be communicated:
<OTA_CancelRS>
...
<UniqueID Type="3" ID="ABCD456782" ID_Context="CorporationRepresentative"/>
...
</OTA_CancelRS>