Used to identify the sequence number of the transaction as assigned by the sending system; allows for an application to process messages in a certain order or to request a resynchronization of messages in the event that a system has been off-line and needs to retrieve messages that were missed.
Indicates the creation date and time of the message in UTC using the following format specified by ISO 8601; YYYY-MM-DDThh:mm:ssZ with time values using the 24 hour clock (e.g. 20 November 2003, 1:59:38 pm UTC becomes 2003-11-20T13:59:38Z).
A reference for additional message identification, assigned by the requesting host system. When a request message includes an echo token the corresponding response message MUST include an echo token with an identical value.
This indicates where this message falls within a sequence of messages.
When true, indicates the message is being re-sent after a failure. It is recommended that this attribute is used (i.e., set to TRUE) only when a message is retransmitted.
Used to indicate whether the request is for the Test or Production system.
The AirDetails Request message is used to request additional flight details for each leg of a flight (e.g. journey time, meal service). The request includes necessary information to identify a specific flight:
- Airline
- Flight Number
- Departure Airport
- Arrival Airport
- Departure Date
Identifes the primary language preference for the message. The human language is identified by ISO 639 codes.
A unique identifier to relate all messages within a transaction (e.g. this would be sent in all request and response messages that are part of an on-going transaction).
For all OTA versioned messages, the version of the message is indicated by a decimal value.
Identifies the alternate language for a customer or message. The human language is identified by ISO 639 codes.