SDK segments are travel segments that are obtained from a third-party provider and do not reside in any Universal API provider's system. To support these segments from external sources, a generic "SDK" provider is used to represent any third-party content booked in the Universal Record. SDK segments do not have any back-end host system.
Currently, air, vehicle, hotel, and passive segments support an SDK provider.
Creating Reservations with an SDK Provider
All fields for creating an air, vehicle, hotel, or passive segment booking are supported in an SDK provider request and response and, for all SDK bookings, the provider code is set and returned as "SDK".
For Air and Passive, the Provider Code is always "SDK". However, Hotel and Vehicle do not automatically default to Provider Code = "SDK", so the ThirdPartyInformation element is used to determine Hotel and Vehicle passive reservations as "SDK". Air and Passive reservations can use ThirdPartyInformation to enter more SDK supplier details.
SDK reservations create a ProviderReservationInfo element in the Universal Record, but because they are not linked to any provider, a locator code is not sent back. Instead, the LocatorCode on ProviderReservationInfo is populated with the Locator Code that Universal API assigns as an attribute inside the Reservation (Air, Vehicle, Hotel, Passive). Universal Record History is updated with the ThirdPartyInformation data using the new value “Party Information”. Any former ThirdPartySupplierName data is recorded in the new value “Third Party Name”.
Feedback / Support
