API Information

Response Format
XML
Service Action Code
FaresContractLoadRQ
Current Version
5.11.0
Target Audience
Both TN and AS
Environment
Production
Documentation
Go to the Upload Fare Contract Data documentation

What's New

  • New fare base attributes can be defined and processed when using creating FaresContractLoadRQ for a Category 25 rule
  • New Passenger Application selection will be added to Category 12 Surcharges
  • Removed Obsolete Routing Restriction Options not supported by ATPCO

Functional Updates And Enhancements

In the Request

Optional

Parameter: Footnote

Type: string

Description: Footnote1 and Footnote2 can be added as attributes

Sample Value:

<FareAttributes> <FareBasis>Y-</FareBasis> <PsgType>ADT</PsgType> <Carrier>AA</Carrier> <Footnote1>#</Footnote1> </FareAttributes> <FareAttributes> <FareBasis>B-</FareBasis> <PsgType>ADT</PsgType> <Footnote2>R4</Footnote2> </FareAttributes>
Parameter: SurchargeApplication

Type: Values: 1,2,3,4

Description: Numeric code can be specified

Sample Value:

<Surcharge> <Type>D</Type> <Amount currency="USD">567.89</Amount> <SurchargeApplication>2</SurchargeApplication> <PassengerApplication>1</PassengerApplication> <InboundOutboundInd>I</InboundOutboundInd> <...> </Surcharge>