This article will address frequently asked questions regarding our APIs.
A: We have three different vesions of APIs. Authentication is handled in the following ways:
- APIv3 is a SOAP based API and uses WS-Security username/password authentication.
- APIv4 is a SOAP based API and uses a standalone session service for authentication. (see this article for further details)
- RESTv1 is a RESTful API with a JSON request/response structure and uses HTTP Basic Auth over a secure channel.
A: We often refer to this type of request as "Travel Options". The recommended API to use is RESTv1 GET travelOptions. See the online documentation for further details.
A: This is referred to as Seat Map retrieval. The recommended approach is to use GetSeatMapByFlight() under the Booking Service in APIv3. For sample requests see this article.
A: Setting seat assignments can be done by using SetSeatAssignmentsByFlight() under the CheckIn Service in APIv3. Refer to this article for a more in depth explanation.
A: There are a few ways to go about doing this. The recommended approach is to use RESTv1 GET reservation available in release 16.10 or later. Alternatively, reservation information can be retrieved using GetReservation() under the CheckIn Service in APIv3.
A: In APIv3 under the User Profile Service there is an operation called GetProfileReservationList(). This will return all reservations associated with the provided user profile information.
A: In APIv3 under the CheckIn Service there is an operation called CheckIn(). If this request is successful the passenger will be checked in for all flights on the Segment passed in the request. Further information can be found here.
A: In APIv3 under the CheckIn Service there is an operation called EmailBoardingPass(). This operation emails the boarding pass for a passenger on a reservation based on the information supplied in the request.
Related articles