Price With Itinerary

1.4.4
Air
Pricing
SOAP API
Travel Agency
Airline Carrier

v1.4.4 | December 18, 2019

  • Price with Itinerary has been enhanced with the following new optional search parameter:
  • Agency Managed Commission functionality schema change.
  • Not acceptable forms of payment - additional information in the response.
  • Fare Type Bitmap - attribute change from required to optional.
Read more

API Information

Response Format
XML
Service Action Code
PO_PNRPricingRQ
Current Version
1.4.4
Target Audience
TN
Environment
Production

What's New

  • Price with Itinerary has been enhanced with the following new optional search parameter:
  • Agency Managed Commission functionality schema change.
  • Not acceptable forms of payment - additional information in the response.
  • Fare Type Bitmap - attribute change from required to optional.

Business Value

New Features

In the Response

Optional

Parameter: LaunchRuleInformation

Type: LaunchRuleInformationType

Description: New element and attributes required in WPRD*CM enhancement to display Fare Break Initiating (Launch) Rule with Fare Break Tag Info.

Sample Value:

<ValidatingCarrierCommissions>
  <ValidatingCarrierCommission ValidatingCarrier="AA" CommissionAmount="45.15" EarnedCommissionAmount="60.39" CommissionContractQualifier="USCAINDHALLOW2" SourcePCC="A1D0">
    <FareComponentBreakdowns>
      <FareComponentBreakdown FareComponentReferenceID="1" FareComponentCommission="24.37" EarnedFareComponentCommission="36.56" MethodID="18175" RuleID="16999" RuleFamilyID="16999" ContractID="14425" ContractFamilyID="14425"/>
      <FareComponentBreakdown FareComponentReferenceID="2" FareComponentCommission="5.95" EarnedFareComponentCommission="5.95" MethodID="18182" RuleID="16999" RuleFamilyID="16999" ContractID="14425" ContractFamilyID="14425"/>
      <FareComponentBreakdown FareComponentReferenceID="3" FareComponentCommission="6.12" EarnedFareComponentCommission="9.18" MethodID="18175" RuleID="16999" RuleFamilyID="16999" ContractID="14425" ContractFamilyID="14425"/>
      <FareComponentBreakdown FareComponentReferenceID="4" FareComponentCommission="8.70" EarnedFareComponentCommission="8.70" MethodID="18182" RuleID="16999" RuleFamilyID="16999" ContractID="14425" ContractFamilyID="14425"/>
    </FareComponentBreakdowns>
    <LaunchRuleInformations>
      <LaunchRuleInformation FareComponentReferenceID="3" LaunchRuleID="16999" FareBreakTagIndicator="H"/>
      <LaunchRuleInformation FareComponentReferenceID="4" LaunchRuleID="16999" FareBreakTagIndicator="H"/>
    </LaunchRuleInformations>
    <TicketingInstruction CommissionVerificationCode="CVCAA" CommissionVerificaitonCodePlacement="TourCode">
      <EndorsementMessage>ENDTEXT AA NO EOE</EndorsementMessage>
    </TicketingInstruction>
  </ValidatingCarrierCommission>
</ValidatingCarrierCommissions>
Note: New part of the schema related to Agency Managed Commission (AMC) functionality.

In the Response

Optional

Parameter: NotAcceptableFormsOfPayment

Type: NotAcceptableFormsOfPaymentType

Description: New parts of the schema in PassangerDetails section regarding acceptable forms of payment.

Sample Value:

<PassengerDetails>
  <PassengerDetail PassengerTypeCode="ADT">
    <NotAcceptableFormsOfPayment CashIsNotAcceptable="true" CreditCardIsNotAcceptable="true" CheckIsNotAcceptable="false" GTRIsNotAcceptable="false"/>
  </PassengerDetail>
</PassengerDetails>
Note: Based on some of the customers' feedback, additional information has been added to the non-acceptable forms of payment. It covers information if given form of payment is not acceptable for given fare. The included forms are: Credit Card, Cash, Check and GTR.

Functional Updates And Enhancements

In the Response

Optional

Parameter: FareTypeBitmap

Type: FareTypeBitmapType

Description: A fare pricing component returned by the carrier if used also in ancillaries records.

Sample Value:

<FareComponents>
  <FareComponent PricingUnitCount="1" PricingUnitType="O" GlobalDirection="AT" FareCalcDirectionality="FR" CommencementDate="2019-12-01" StopoverInd="false" CabinCode="S" BrandId="PECFL" BrandName="PREMIUM ECONOMY FLEXIBLE" ProgramCode="AAAT" ProgramName="AABFAT1S" ProgramSystemCode="B" ProgramID="154838" FareTypeBitmap="00">
    </FareComponent>
</FareComponents>
Note: Attribute FareTypeBitmap added in 1Q Release, changed from required to optional.

Relase note ID: 13681

v1.4.3 | March 28, 2019

  • Price with Itinerary has been enhanced with the following new optional search parameter:
  • Source PCC - The source PCC of the contract processed for Agency Managed Commission will be added for audit and tracking purposes
  • Fare Type Bitmap - A fare pricing component related to ancillaries offer
Read more

API Information

Response Format
XML
Service Action Code
PO_PNRPricingRQ
Current Version
1.4.3
Target Audience
TN
Environment
Production

What's New

  • Price with Itinerary has been enhanced with the following new optional search parameter:
  • Source PCC - The source PCC of the contract processed for Agency Managed Commission will be added for audit and tracking purposes
  • Fare Type Bitmap - A fare pricing component related to ancillaries offer

Business Value

  • Source PCC supports the agencies configuration in terms of managing commissions. Fare Type Bitmap enhances the options available while shopping and pricing the ancillaries offer.

New Features

In the Response

Optional

Parameter: SourcePCC

Type: PseudoCityCodeType

Description: The PCC of the contract processed for Agency Managed Commission which is added for audit/tracking purposes.

Sample Value:

<Summary>
  <PassengerDetails>
    <PassengerDetail>
      <ValidatingCarrierCommissions>
        <ValidatingCarrierCommission SourcePCC="A1D0">              </ValidatingCarrierCommission>
      </ValidatingCarrierCommissions>
    </PassengerDetail>
  </PassengerDetails>
</Summary>
Note: Source PseudoCityCode

In the Response

Optional

Parameter: FareTypeBitmap

Type: FareTypeBitmapType

Description: A fare pricing component returned by the carrier if used also in ancillaries records.

Sample Value:

<PassengerDetails>
  <PassengerDetail>
    <PassengerFare>
      <FareCalculation>
        <FareComponents>
          <FareComponent FareTypeBitmap="04"/>
        </FareComponents>
      </FareCalculation>
    </PassengerFare>
  </PassengerDetail>
</PassengerDetails>
Note: FareTypeBitmap represents sum of following possible values: 0x00 - Normal, 0x01 - Discounted, 0x02 - Fare by Rule, 0x04 - Negotiated, 0x08 - Private, Eg. 0x06 = Fare by Rule Negotiated.

Relase note ID: 12829

v1.3.9 | June 27, 2018

  • Price with Itinerary has been enhanced with the following new optional search parameter:
  • Special Service Request Code
Read more

API Information

Response Format
XML
Service Action Code
PO_PNRPricingRQ
Current Version
1.3.9
Target Audience
TN
Environment
Production

What's New

  • Price with Itinerary has been enhanced with the following new optional search parameter:
  • Special Service Request Code

Business Value

  • This new optional parameter provides an efficient way for customers to list and price ancillaries when the ancillary of interest is known.

New Features

In the Request

Optional

Parameter: Code

Type: SpecialServiceType

Description: Special service request code.

Sample Value:

<SSR>
  <SSC Code="SEAT"/>
  <SSC Code="UMNR"/>
</SSR>
Note:

Relase note ID: 12948

v1.3.8 | March 27, 2018

  • Price with Itinerary has been enhanced with new optional search parameters
  • Multi Ticket capability for traditional and low-cost carriers, that also allows multi ticket combination of both carrier types.
Read more

API Information

Response Format
XML
Service Action Code
PO_PNRPricingRQ
Current Version
1.3.8
Target Audience
TN
Environment
Production

What's New

  • Price with Itinerary has been enhanced with new optional search parameters
  • Multi Ticket capability for traditional and low-cost carriers, that also allows multi ticket combination of both carrier types.

Business Value

  • The Multi Ticket capability provides more attractive faring options being returned by the pricing service, as a combination of two separate tickets (a traditionally ticketable carrier and a low-cost Instant Purchase carrier).

New Features

In the Request

Optional

Parameter:

Type:

Description:

Sample Value:

 
Note:

Functional Updates And Enhancements

In the Request

Optional

Parameter: MultiTicket/@Ind

Type: Boolean

Description: Ability to indicate whether or not Multi Ticket options are being requested. @Ind="true" requests Multi Ticket options being returned in the response, while @Ind="false" or disables the feature.

Sample Value:

<PriceRequestInformation BuyingDate="2016-06-14T05:19:00" CurrencyCode="USD">
  <PassengerTypes>
    <PassengerType Code="ADT" Count="01"/>
  </PassengerTypes>
  <ApplyOBFees Ind="true"/>
  <ApplyOCFees Ind="true"/>
  <ReturnAllData Value="1"/>
  <EticketableFare Ind="true"/>
  <FreeBaggageSubscriber Ind="true"/>
  <MultiTicket Ind="true"/>
</PriceRequestInformation>
Note:

In the Response

Optional

Parameter: @MultiTicketResponse

Type:

Description:

Sample Value:

 
Note:

Relase note ID: 13091