Air Booking with OSIs

Other Service Information (OSI) requests are messages sent directly to the supplier to communicate traveler preferences or requirements. OSIs are used only for air segments. OSIs are typically used to notify a supplier of special circumstances such as a passenger that does not speak the local language.

Unlike SSRs, OSIs are informational only and do not require the supplier to take action.

Schema

Located in Universal.xsd:

• AirCreateReservationReq
• AirCreateReservationRsp

How To

1. Include the minimum required information for creating an air booking.

2. Include one or more OSIs using AirCreateReservationReq/OSI. Unlike SSRs, OSIs are assigned generically to the entire booking, not to individual travelers within a booking.

   • @Carrier is the supplier code of the air carrier.

   • @Text contains the OSI message. Universal API supports 256 characters, however, the amount text that can be processed by each provider varies.

   • @ProviderCode indicates the provider associated with the booking and @ProviderReservationInfoRef indicates the record locator for the PNR.

   • @Code is optional and can be used to further qualify the OSI. This attribute is not supported on Galileo and ACH.

3. The response returns an Air Booking with OSI information located in AirCreateReservationRsp/UniversalRecord/AirReservation/OSI.

   If multiple OSIs are added in a single request and one message fails, the valid OSIs are successfully added to the PNR and only the faulty message is missing from the response.

   Some ACH carriers do not support OSIs. For those carriers, the following warning message may be returned for one or more carriers: XX carrier may not support the requested OSI.

Exceptions

Galileo

The maximum number of OSI characters on Galileo is 99.

ACH

The maximum number of OSI characters on ACH is 64.