Here you will find APIs used to price and sell flight segments for a trip, and include important travel extras as part of the process. You can also extend your application’s workflow to manage other aspects of an air booking such as selecting a seat.

Name Category Function API Type Link

  Alert! There are no items that match your filter.

Air Fare Rules (OTA_AirRulesLLSRQ) is used to display air fare rules, based upon city pair, date, fare basis code and carrier code. Examples of what you can specify include to return fare routing-related information, a global indicator, a ticket designator, an account code, a corporate ID, a private or public fare indicator, display historical fare rules based upon a fare basis code, date, class of service, as well as a carrier code. Go to documentation

Air Fare Rules from Price (PO_RulesFromPriceRQ) supports the fare and rule display of fares from the response of No PNR Pricing. It can display rules for up to 16 fares from fare option response of No PNR pricing within a single request. It can also display rule menu, header and routing information by request. Go to documentation

Air Fares by City Pairs (FareLLSRQ) is used to search for fares associated with particular markets. Using this API, you can perform a basic fare quote, specify preferred airlines, specify a currency code, specify to return base fare and tax information, specify an account code, specify a corporate ID, specify a fare basis code, specify a fare level, specify a global indicator, specify a fare basis code/ticket designator, and several other parameters. Go to documentation

Book Air Segment (OTA_AirBookLLSRQ) is used to book one or more flight segments. Using this API, you canbook a one way or round trip itinerary, or book an open itinerary. Other parameters include equipment and flight information, number in party, origin and destination information, booking code. Go to documentation

Book from Air Availability (ShortSellLLSRQ) is used to short sell direct access airline flight segments from an air availability response. You can also specify a married connection from a successful, direct access-based Air Availability response, or request with multiple connections/booking classes. Go to documentation

Calculate Air Tax for Itinerary (OTA_AirTaxRQ) is used to calculate applicable taxes for one or more air travel itineraries, and for one or more passenger types on each itinerary. This service can calculate taxes for up to 50 itineraries. Each itinerary can contain multiple flight segments and multiple fare break points. Go to documentation

Cancel Air Seat (AirSeatCancelLLSRQ) is used to cancel a previously reserved seat for a selected itinerary segment. Go to documentation

Cancel Itinerary Segments (OTA_CancelLLSRQ) is used to cancel itinerary segments contained within a passenger name record (PNR). Go to documentation

Orchestrated APIs bundle several functions and operations into a single API call thus maximizing development efforts and providing operational efficiencies by calling multiple services to fulfill a desired workflow. Go to documentation

Delete Price Quote (DeletePriceQuoteLLSRQ) is used to delete price quote records. Please note that a PNR must be present in the current work area/session prior to calling this API. Go to documentation

Display Price Quote (DisplayPriceQuoteLLSRQ) is used to display stored fare information contained within a passenger name record (PNR). Go to documentation

Fare Rules from Air Price (RulesFromPriceLLSRQ) is used to retrieve fare rule information from a pricing response. OTA_AirPriceLLSRQ must be executed prior to calling RulesFromPriceLLSRQ. Go to documentation

Flight Details (VerifyFlightDetailsLLSRQ) is used to verify details about a specific flight number on a specific date. Using this API, you can verify flight details for a range of lines in a Get Air Availability response or verify flight details for multiple, nonconsecutive lines in a Get Air Availability response. Go to documentation

Orchestrated Air Booking (EnhancedAirBookRQ) is used to book, price, and compare prices for a maximum of 99 flight segments. Before using this service, it is assumed that the client has completed shopping and has chosen flights to sell. Go to documentation

Price Air Itinerary (OTA_AirPriceLLSRQ) is used to price air itineraries. There must be at least one flight segment in the current work area/session with two seats sold. Go to documentation

Price with Itinerary (PO_PNRPricingRQ) is used to support PNR Pricing (also referred as Itinerary Pricing) functionality. Many parameters are provided in this API including, currency code, base fare amount, price, fare basis code, passenger type, airline code, security fee, nation and station code, arrival and departure code, and ancillary fee group code. Go to documentation

Price without Itinerary (PO_NoPNRPricingRQ) is used to support No PNR Pricing functionality. This API prices up to 16 segments and up to a maximum of four passenger types without a PNR. It provides up to 24 fare options per passenger type. Go to documentation

Reserve Air Seat (AirSeatLLSRQ) is used to reserve a seat for an itinerary segment or segments. Go to documentation

Seat Map (EnhancedSeatMapRQ) used to display seat map with prices, for a given carrier code, flight number, class of service, board point, off point and departure date. Information returned response contains the seat map data and the exact prices for each paid seat, in addition to a seat map banner. Go to documentation

Sell Miscellaneous Segment (MiscSegmentSellLLSRQ) is used to sell OTH, MCO, PTA, or INS miscellaneous segment types. Go to documentation

Docs Navigation