FareRules 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
<FareRulesRS>
Fare rules response root element1
@version
Version number. 0..1 1.0
<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>
<DepartureCity/>
Departure city. 1 MIA
<ArrivalCity/>
Arrival city. 1 JFK
<DepartureDate/>
Departure date in ISO 8601 format (yyyy-mm-dd). 1 2001-10-01
<AirlineCode/>
Airline code. 1 AA
<FareBasisCode/>
Fare basis code. 1 Y26
<TicketDesignator/>
Ticket designator code.

0..1 ATM1
<FareType/>
Fare type. 0..1 Normal
<Rule>
Rule group0..N
@Category
Fare rule category associated with the fare basis code.
Possible values are:
ACC=Accompanied Travel
ADD=Add-Ons
AGT=Agent Discounts
APP=Rule Application
BLA=Blackout Dates
BOC=Booking Code
CHD=Children Discounts
CMB=Combinability
COT=Co-Terminals
CTC=Circle Trip Combinability
DAY=Day and / or Time Application
DEP=Deposits
DSC=All Other Discounts
END=Ticket Endorsements
EOE=End On End Combinability
EXD=Effective/Expiration Dates
FBR=Fare By Rule
FLT=Flight Application
FTR=First Travel
GRP=Groups
HEA=Rules Header
HIP=Higher Intermediate Point / Mileage Exceptions
ICT=International Construction
LIS=List All Restrictions
MAX=Maximum Stay
MIN=Minimum Stay
MIS=Miscellaneous Provisions
NET=Negotiated Fares
OPJ=Open Jaw Combinability
ORE=Open Return
OTH=Other
PEN=Penalties
REF=Refunds
RER=Reroute
RES=Advance Reservation / Ticketing Restrictions
ROU=Routings
SEA=Seasonality
SPP=Special Provisions
STP=Stopovers
SUR=Surcharges
TCO=Tour Conductor Discounts
TKT=Sales Restrictions
TOU=Tours
TRF=Transfers
TVL=Travel Restrictions
VCT=Visit Another Country
VOL=Voluntary Changes
VRF=Voluntary Refunds
WHO=Eligibility

TNC=Terms and Conditions; for low cost carriers (Air Arabia) only

[ACC] [ADD] [AGT] [APP] [BLA] [BOC] [CHD] [CMB] [COT] [CTC] [DAY] [DEP] [DSC] [END] [EOE] [EXD] [FBR] [FLT] [FTR] [GRP] [HEA] [HIP] [ICT] [LIS] [MAX] [MIN] [MIS] [NET] [OPJ] [ORE] [OTH] [PEN] [REF] [RER] [RES] [ROU] [SEA] [SPP] [STP] [SUR] [TCO] [TKT] [TNC] [TOU] [TRF] [TVL] [VCT] [VOL] [VRF] [WHO] 1 PEN
<Text/>
Information text or error text. 1..N Free flow text. Example: Invalid flight number
</Rule>
<ProviderURL/>
Link to provider website which displays terms and conditions for this carrier (only for low cost carrier so far).1
</FareRulesRS>

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