TicketRevalidation 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
<TicketRevalidationRQ>
Ticket Revalidation Request1
@version
Version number. 0..1 1.0
@Source
Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. 0..1 1A, 1V, or other.
<TicketNumber>
The 13-digit ticket number (no check digit) holding the coupon(s) to be validated against flight segment(s) of the PNR. In case of a conjunctive ticket, tis must be the first ticket number of the conjunctive set.
1 1761234567890
@ValidatingCarrier
0..1
</TicketNumber>
<RecordLocator>
Record locator of the PNR holding the new flight segment to be validated against the coupon of a previously issued ticket.
1 R1A3SK
</RecordLocator>
<ValidationRequest>
A set of data to associate an issued ticket coupon number with a newly booked segment number1..N
<TicketData>
Data of the coupon to be validated. .1
@TicketSetNumber
In case of a conjunctive ticket set, the last three digits (no check digit) of the actual ticket within the set needs to
0..1 890
<CouponNumber>
The number of the coupon to be validated.
1 1
@NotValidBefore
If the fare does not permit travel to be commenced or completed before a certain date.0..1
@NotValidAfter
Date by which travel must be commenced/completed.0..1
@CouponStatus
The IATA coupon status code. Possible values:
A AIRPORT CONTROL
C CHECKED IN
E EXCHANGED / REISSUED
F FLOWN/USED
G CONVERTED TO FIM
I IRREGULAR OPERATIONS
L LIFTED/BOARDED
N COUPON NOTIFICATION
O OPEN FOR USE
P PRINTED
R REFUNDED
S SUSPENDED
T PAPER TICKET U UNAVAILABLE
V VOID
X PRINT EXCHANGE
Z CLOSED
[A] [C] [E] [F] [G] [I] [L] [N] [O] [P] [R] [S] [T] [U] [V] [X] [Z] 0..1
</CouponNumber>
<CouponDetails>
Supplementary coupon details if needed by source system in addition to the CouponNumber.0..1
<Departure>
1
<AirportCode/>
IATA standard airport code .
1 MIA
<AirportName/>
Name of the airport identified in AirportCode element.
1 MIAMI INTERNATIONAL
<Date/>
Date of departure. ISO format: yyyy-mm-dd
1 2008-12-12
<Time/>
Time in ISO 8601 hh:mm format.
0..1 14:00
<Terminal/>
Airport terminal.
0..1 2B
</Departure>
<Arrival>
1
<AirportCode/>
IATA standard airport code .
1 MIA
<AirportName/>
Name of the airport identified in AirportCode element.
1 MIAMI INTERNATIONAL
<Date/>
Date of departure. ISO format: yyyy-mm-dd.
0..1 2008-12-12
<ChangeOfDay/>
Number of days between departure and arrival. If not present - no change of day - same day as departure.
0..1 1
<Time/>
Time in ISO 8601 hh:mm format.
0..1 14:00
<Terminal/>
Airport terminal.
0..1 2B
</Arrival>
<Carrier>
1
<AirlineCode/>
IATA Airline code. 1 AA
<AirlineName/>
Airline name. 0..1 American Airlines
<FlightNumber>
0..1
@Suffix
Flight number alpha qualifier. Values are:
A
B
C
D
[A] [B] [C] [D] 0..1 A
</FlightNumber>
</Carrier>
<ClassOfService/>
Class of service. 1 B
</CouponDetails>
</TicketData>
<PNRData>
Data of the PNR flight segment to be validated.1
<SegmentNumber/>
The number of the flight segment to be validated.
1 3
<SegmentDetails>
Supplementary coupon details if needed by source system in addition to the CouponNumber.0..1
<Departure>
1
<AirportCode/>
IATA standard airport code .
1 MIA
<AirportName/>
Name of the airport identified in AirportCode element.
1 MIAMI INTERNATIONAL
<Date/>
Date of departure. ISO format: yyyy-mm-dd
1 2008-12-12
<Time/>
Time in ISO 8601 hh:mm format.
0..1 14:00
<Terminal/>
Airport terminal.
0..1 2B
</Departure>
<Arrival>
1
<AirportCode/>
IATA standard airport code .
1 MIA
<AirportName/>
Name of the airport identified in AirportCode element.
1 MIAMI INTERNATIONAL
<Date/>
Date of departure. ISO format: yyyy-mm-dd.
0..1 2008-12-12
<ChangeOfDay/>
Number of days between departure and arrival. If not present - no change of day - same day as departure.
0..1 1
<Time/>
Time in ISO 8601 hh:mm format.
0..1 14:00
<Terminal/>
Airport terminal.
0..1 2B
</Arrival>
<Carrier>
1
<AirlineCode/>
IATA Airline code. 1 AA
<AirlineName/>
Airline name. 0..1 American Airlines
<FlightNumber>
0..1
@Suffix
Flight number alpha qualifier. Values are:
A
B
C
D
[A] [B] [C] [D] 0..1 A
</FlightNumber>
</Carrier>
<ClassOfService/>
Class of service. 1 B
<ActionCode>
1
@Status
Identifies for HK codes if the sell is confirmed (sold in carrier system). Values are:
K - confirmed
U - unknown
1
</ActionCode>
</SegmentDetails>
</PNRData>
</ValidationRequest>
<ChangeFee>
Change Fee Information0..1
<MCONumber/>
The 13-digit MCO number used to collect any associated change fee.
1 1761234567890
<CurrencyCode>
Currency code. 1 USD
@NumberOfDecimals
Decimal position in fare amount. 1 2
</CurrencyCode>
<Amount/>
Amount of Change Fee collected via MCO
1 6500
</ChangeFee>
<ReasonText/>
Any additional Freeflow text transmitted to airline.
0..1 "No Change Fee applies" or "Fee verified as per Fare Rules""
</TicketRevalidationRQ>

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