Tax request message

Tabular overview of all nodes, which may occur in this message. See legend below for description of table columns.
Note: Some sibling elements or complete sub-trees of the hierarchy may be defined as mutually exclusive alternative choices. This information cannot be expressed in this tabular overview. Please refer to schema diagram for a graphical representation of the message schema.

NodeDescriptionValuesOccursExample
<TaxRQ>
Message to calculate taxes per passenger type for a itinerary of specified flights.1
<SaleInfo>
Sale Information group0..1
<CityCode/>
City where sale takes place or City where ticket will be issued. 0..1 MIA
<CountryCode/>
Country where sale takes place or Ticket issuing country. 0..1 US
<CurrencyCode>
0..1
</CurrencyCode>
<PseudoCityCode/>
Agency's pseudo city code. 0..1 LNJ2
</SaleInfo>
<TicketingInfo>
Ticketing Information group0..1
<CityCode/>
City where sale takes place or City where ticket will be issued. 0..1 MIA
<CountryCode/>
Country where sale takes place or Ticket issuing country. 0..1 US
<Date/>
Specifies ticketing date in ISO 8601 format (yyyy-mm-dd).
0..1 2001-12-25
</TicketingInfo>
<TravelerInfo>
Traveler type for which taxes will be requested.1..N
@Type
Passenger type requested for taxes. If the passenger type sent to the GDS is not in the below predefined list, then it is passed as is to the GDS.
Predefined values are :
ADT= Adult
CHD = Child
INF = Infant
GOV = Government
MIL = Military
SRC = Senior citizen
STD = Student
YTH = Youth
1 CHD
@TravelerInfoID
Unique traveler info ID, that is used to refer to traveler types from a Fare element.

1 T1
</TravelerInfo>
<Flight>
Flights, the taxes are calculated for.1..N
@TypeIndicator
Type indicator, which indicates whether this flight is connected to following flight or a stopover flight.

If departure airport code of the following flight differs from arrival airport code of this flight, this indicates the existance of a surface segment.
In this case a value of X indicates a surface connection segment.
A value of O indicates a surface stopover segment also known as ARNK.

[X] [O] [N] 0..1 X .. Connected O .. StopOver N .. Non-Stop (default)
@FlightID
Unique flight ID, that is used to refer to flights from a Fare element.

1 F1
<AirlineCode/>
Airline Code. 1 DL
<FlightNumber>
Flight number - an integer value within the range of [0,9999].

0..1 1234
@Suffix
Flight number alpha qualifier.
Values are:
A
B
C
D

[A] [B] [C] [D] 0..1 A
</FlightNumber>
<ClassOfService/>
Class of service. 1 B
<Departure>
Departure Information group1
<AirportCode/>
Origin or destination Airport Code. 1 MIA
<Date/>
Specifies departure date in ISO 8601 format (yyyy-mm-dd). 1 2001-12-25
<Time/>
Departure time in ISO 8601 twenty-four hour clock format. 0..1 14:00
</Departure>
<Arrival>
Arrival Information group1
<AirportCode/>
Origin or destination Airport Code. 1 MIA
<Date/>
Specifies arrival date in ISO 8601 format (yyyy-mm-dd). 0..1 2001-12-25
<Time/>
Arrival time in ISO 8601 twenty-four hour clock format. 0..1 14:00
</Arrival>
<Equipment>
Flight equipment group0..1
<Code/>
Equipment type code. 1 747
</Equipment>
</Flight>
<Fare>
Fare that may apply to different flights and traveler types.0..N
<TravelerInfoIDRef/>
1..N
<FlightIDRef/>
1..N
<FareBasisCode/>
FareBasisCode information is needed for YQ/YR tax information1
<BaseFare>
Base fare amount in amount attribute.

Amount is required to calculate the percentage taxes
1
@Amount
Total base fare amount that includes surcharges (if any). 1 200000
<FiledIn>
This group represents fares filed in a currency different from the currency of a point of sale. The content elements represent the original currency and amount as filed.0..1
<CurrencyCode>
Currency code. 1 USD
@NumberOfDecimals
Decimal position in fare amount. 1 2
</CurrencyCode>
<Amount/>
Base Fare Amount as originally filed.1
</FiledIn>
</BaseFare>
<CurrencyCode>
Currency code. 1 USD
@NumberOfDecimals
Decimal position in fare amount. 1 2
</CurrencyCode>
</Fare>
<ValidatingCarrier/>
Validating Carrier.

0..1 AA
</TaxRQ>

Legend

ColumnDescription
NodeName of message node (element or attribute). Nodes in bold type are mandatory, if their parent element occurs in the message. Point mouse cursor at table cell to view complete XPath.
DescriptionDescription of meaning and usage of the node.
ValuesList of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema.
OccursMinimum and maximum number of times the node must/may occur, if its parent element occurs in the message. Examples:
0..3 Node is optional and may occur up to 3 times.
1..N Node must occur at least one (mandatory) and may occur any number of times.
2 Node must occur exactly twice.
ExampleExample value for the node.

XML Schema documentation generated with XX/1 server