Skip to main content

Orchestrated Air Booking

3.10.0
Air
Pricing
SOAP API
Travel Agency
Airline Carrier
  • Enhanced AirBook now supports Multiple Pricing Requests/Responses within a single Enhanced AirBook request
  • Halts Enhanced AirBook, when price drops from a user specified value
  • Upgraded OTA_AirPriceLLSRQ to 2.16.0
  • BugFix made to not to convert the segment status to “QF” by default, when InstantPurchase=”true” and IgnoreAfter=”true”

API Information

Response Format
XML
Service Action Code
EnhancedAIrBookRQ
Current Version
3.9.0
Target Audience
TN
Environment
Production

What's New

  • Enhanced AirBook now supports Multiple Pricing Requests/Responses within a single Enhanced AirBook request
  • Halts Enhanced AirBook, when price drops from a user specified value
  • Upgraded OTA_AirPriceLLSRQ to 2.16.0
  • BugFix made to not to convert the segment status to “QF” by default, when InstantPurchase=”true” and IgnoreAfter=”true”

New Features

In the Request

Optional

Parameter: AcceptablePriceDecrease

Type: positiveAmount

Description: It is used to specify an Amount or Percent, below which the final pricing for a booking should not be reduced

Sample Value:

 
Note:

In the Request

Optional

Parameter: Amount, Percent

Type: positiveAmount

Description: Amount is used to specify the user anticipated amount. Percent is used to specify the user anticipated percent

Sample Value:

 
Note:

In the Request

Optional

Parameter: HaltOnNonAcceptablePrice

Type: Boolean

Description: HaltOnNonAcceptablePrice is used to specify, whether service should stop when actual price is lower than "AmountSpecified" percent or amount decrease

Sample Value:

 
Note:

Resolved Issues

In the Request/Response

Optional

Currently when InstantPurchase=”true” and IgnoreAfter=”true”, EAB internally converts the segment status to “QF” by default. With the fix in the new version of EAB, segment status will not be changed to “QF” by default when InstantPurchase=”true” and IgnoreAfter=”true”

Relase note ID: 13000


  • Upgrade TravelItineraryReadRQ to 3.8.0
  • New feature to book API carriers

API Information

Response Format
XML
Service Action Code
EnhancedAirBookRQ
Current Version
3.8.0
Target Audience
TN
Environment
Production

What's New

  • Upgrade TravelItineraryReadRQ to 3.8.0
  • New feature to book API carriers

New Features

In the Request

Optional

Parameter: InstantPurchase

Type: Boolean

Description: When |-|AirItineraryPricingInfo PricingSubSource="API”|--| from BargainFinderMax API, then InstantPurchase attribute in EAB should be set to true, for booking API carriers.

Sample Value:

 
Note:

In the Response

Optional

Parameter: Group

Type: String

Description: A set of air segments that are considered “married” together. This is referred to as the new married group number. Married Group may contain up to 3 segments.

Sample Value:

<OTA_AirBookRS>.<MarriageGrp Group="1" Sequence="2"/> .</OTA_AirBookRS>
Note:

In the Response

Optional

Parameter: Sequence

Type: String

Description: The sequence number within the set/group of air segments that considered “married” together.

Sample Value:

<OTA_AirBookRS> .<MarriageGrp Group="1" Sequence="2"/> . . </OTA_AirBookRS>
Note:

Relase note ID: 13045


  • Upgraded OTA_AirPrice to 2.13.0

API Information

Response Format
XML
Service Action Code
EnhancedAirBookRQ
Current Version
3.7.0
Target Audience
TN
Environment
Production

What's New

  • Upgraded OTA_AirPrice to 2.13.0

New Features

In the Request

Optional

Parameter: ASLBreakdown, ASLIgnore

Type: Boolean

Description: The above parameters are added under FareOptions element

Sample Value:

 
Note:

In the Request

Optional

Parameter: BasicEconomyExclude

Type: String

Description: BasicEconomyExclude is used to exclude Basic Economy Fares (up to 5 booking classes can be selected)

Sample Value:

 
Note:

In the Request

Optional

Parameter: Cabin

Type: String

Description: Cabin is used to instruct the system to specify fares by a specific cabin or the lowest fare across all cabins

Sample Value:

 
Note:

In the Request

Optional

Parameter: BeforeDeparture, AfterDeparture

Type: Boolean

Description: The above parameters are added under Changeable, EitherOr and Refundable Elements BeforeDeparture is used to query for before depature fees AfterDeparture is used to query for after depature fees

Sample Value:

 
Note:

In the Request

Optional

Parameter: Reference

Type: Integer

Description: The above parameter is added under FOP_Qualifiers.BasicFOP, MultipleFOP.FOP_One, MultipleFOP.FOP_Two, MultipleMiscFOP. FOP_One, MultipleMiscFOP. FOP_Two, PayLaterPlan.FOP, Installment. Reference is used to reference a line number from PNR FOP field

Sample Value:

 
Note:

In the Response

Optional

Parameter: FareBasisCode

Type: String

Description: Fare basis is used to return the related fare basis code

Sample Value:

 
Note:

In the Response

Optional

Parameter: FareComponent

Type: String

Description: Fare basis is used to return fare component number

Sample Value:

 
Note:

Functional Updates And Enhancements

In the Response

Optional

Parameter:

Type:

Description: Updated DivideParty element with maxOccurs parameter

Sample Value:

 
Note:

Resolved Issues

In the Request

Optional

Code, ExpireDate and Number parameters are changed to optional from required. Parameter “Type” under MultipleMiscFOP. FOP_Two is changed to optional from required

Relase note ID: 13112