EventAvailability response 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
<EventAvailabilityRS>
Event availability response root element (Jonview)1
<InfoGroup>
Error and information group0..1
<ForInfo>
Information group0..N
@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.
@SourceRef
PNR Record Locator associated to Source attribute.0..1
<Text/>
Information text or error text. 1..N Free flow text. Example: Invalid flight number
</ForInfo>
<Error>
Error group0..N
@ErrorType
Type of error. 1 Air
@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.
@SourceRef
PNR Record Locator associated to Source attribute.0..1
<Code/>
Error code or equipment type code. 1 0104 (error code), 747 (equipment code)
<Text/>
Information text or error text. 1..N Free flow text. Example: Invalid flight number
<UnderlyingError>
Errors of the backend system can be returned here.0..N
@Code
error code of the backend system.0..1
<Text/>
Information text or error text. 0..N Free flow text. Example: Invalid flight number
</UnderlyingError>
</Error>
<BackOffice>
Generic back office response container. Serves as a placeholder for any context specific content.0..1
</BackOffice>
</InfoGroup>
<Event>
0..N
@EventCode
Event code.
1 LEMAS1
@Quantity
Herein a number specific for the event (product) has to be given; it belongs to a unit applicable for the specific product (feet, days, nights, hours, minutes, ...).
0..1 45
<StartDate/>
Start date in ISO 8601 format (yyyy-mm-dd).
1 2013-08-13
<NumberOfPersons/>
Number of persons per event incl. children.
[1] to []1 1
<Child>
Child elements per event - one per requested child.0..N
@Age
Age of child in years (allowed values are 0-18).
The age should be specified for the StartDate.
[0] to [18]1
</Child>
<EventDescription>
0..1
<Text/>
This is also called productname in the Jonview interface.
1 1 DAY LIFT - LE MASSIF
</EventDescription>
<CurrencyCode>
Currency code of the currency, in which all curreny amount values are returned. This will either be a default currency or the alternate currency specified in the request (if any).

1 CAD
@NumberOfDecimals
Decimal position in fare amount. 1 2
</CurrencyCode>
<TotalAmount/>
Total amount for the booked event (for all persons).
1 25000
</Event>
</EventAvailabilityRS>

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