CarFeatures 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
<CarFeaturesRQ>
Car features request root element1
@version
Version number. 0..1 1.0
<CarVendorCode>
Car vendor code. 1 ZI
@LinkType
Link Type.

Values are:
GCM = Galileo carmaster only participant
GCO = Galileo carmaster only participant secondary
GLP = Galileo link partner
GLO = Galileo link partner secondary
GIA = Galileo inside availability link
GIO = Galileo inside availability link secondary
ASA = Amadeus standard access
ACA= Amadeus complete access
ACP= Amadeus complete access plus
SDA= Sabre direct connect access
SDC= Sabre direct connect sell
SOL= Sabre other link type
WAP= WebSphereDIR
WMP= WebSphereDIR
WNA= WebSphereDIR

Mandatory for Amadeus.

[GCM] [GCO] [GLP] [GLO] [GIA] [GIO] [ASA] [ACA] [ACP] [SDA] [SDC] [SOL] [WAP] [WMP] [WNA] 0..1 ASA
@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.
</CarVendorCode>
<PickUp>
Pick up group1
<Location>
Location group1
<CityCode/>
City code. 1 MIA
<Category/>
Car location category.
Values are:
T = Airport terminal
O = Off-airport
C = City location
P = Port
X = Rail
N = North suburban
E = East suburban
S = South suburban
W = West suburban
A = All suburban locations
R = Resort location
D = default location for the city
F = Chauffeur Drive Station
* = content of Number element contains complete location code (city code is ignored)

[A] [C] [D] [E] [F] [N] [O] [P] [R] [S] [T] [W] [X] [*] 0..1 T
<Number/>
Location number. 0..1 001
</Location>
<Date/>
Date in ISO 8601 format (yyyy-mm-dd). 1 2002-02-22
</PickUp>
<DropOff>
Drop off group1
<Location>
Location group1
<CityCode/>
City code. 1 MIA
<Category/>
Car location category.
Values are:
T = Airport terminal
O = Off-airport
C = City location
P = Port
X = Rail
N = North suburban
E = East suburban
S = South suburban
W = West suburban
A = All suburban locations
R = Resort location
D = default location for the city
F = Chauffeur Drive Station
* = content of Number element contains complete location code (city code is ignored)

[A] [C] [D] [E] [F] [N] [O] [P] [R] [S] [T] [W] [X] [*] 0..1 T
<Number/>
Location number. 0..1 001
</Location>
<Date/>
Date in ISO 8601 format (yyyy-mm-dd). 1 2002-02-22
</DropOff>
<CarType>
Car type code for car type specific search.
GDS use car types defined by standard interline practices and procedures (SIPP) manual. Each car-type code consists of four letters, one letter from each of the following categories :
- CLASS
- TYPE
- SHIFT
- AIR CONDITIONING.
i.e. ECMR = Economy Class + 2/4 Door Car + Manual Transmisson + Air-Conditioning.

You can use asterisks in any position to indicate all. So to search for any car so long as it is automatic, enter: **A* . You can use up to 3 asterisks ( **** not allowed).

CLASS:
C = Compact
E = Economy
F = Full Size (4-door)
I = Intermediate
L = Luxury
M = Mini
P = Premium
S = Standard
X = Special

TYPE:
B = 2-Door
C = 2/4 Door
D = 4-Door
F = 4-Wheel Drive
J = All Terrain
K = Truck
L = Limousine
P = Pick Up
R = Recreational
S = Sports Car
T = Convertible
V = Van
W = Station Wagon
X = Special

SHIFT:
A = Automatic
M = Manual

AIR CONDITIONING:
N = No
R = Yes
1 ECAR
@CodeType
Type of the CarType code.

If not specified the specified CarType is handled as SIPP code. For systems that dont support SIPP codes the vendorspecific type must be used instead.

Values:
SIPP .. SIPP code
VS .. vendor specific code

[SIPP] [VS] 0..1
</CarType>
<RateCode>
Rate code. 1 STD
@Type
Rate Type. Values are: D = Daily
E = Weekend
W = Weekly
M = Monthly
H = Hourly
[D] [E] [W] [M] [H] 0..1 W
</RateCode>
<FeatureType>
Car Features Type. If omitted, a list of Feature Types, that correspond to the search criteria would be returned. Possible values
AGE = Age requirements
CARS = Car vehicle types
CDW = Collision damage waiver
DROP = Dropoff oneways
EXPR = Express service
GAS = Refueling policy
HOURS = Hours operation
INS = Insurance coverage
PAI = Personal Accident insurance
SHTTL = Shuttle service
SPEQ = Special equipment
TAX = Tax - state and local
ADD = Additional location
COMM = Commission
CRED = Credit card info
EQUIP = Special Equipment requests
MISC = Miscellaneous info
NEWS = Hot news items
PYMT= Payment accepted
PROM = Promo/Market info
PKUP = Pickup/Return info
PHON = Phone information
POLY = Policies and requirements
RATE = Rate info
SPCL = Special services
VALID = Drivers license requirements
ADDR = Area office ctc
CLUB = Club membership
CONT = Contacts
CONV = Convention rates
CORP = Corporate rates
FORM = Formats
FUN = Fun activity
FQTV = Frequent Traveler
GEN = General info
GRPS = Groups
GOVT = Government rates
HELP= How to book - help
INTL = International info
SAFE = Safety
TIPS = Industry discounts
TOUR = Tour info
TITLE = Vendor official name
ARRV = Arrival info
XBORD = Cross border info
DELIV= Delivery and collection
0..3 GEN
@SubMenu
The sub menu can specify more precisely the FeatureType element. The sub menu can be returned by Galileo and therefore can be resent to Galileo in the following request to get more information about the Feature. When SubMenu is used, only one FeatureType can be sent to Galileo. 0..1 FQTV
</FeatureType>
<ReferenceKey/>
Reference data base key. 0..1 12345678 Mandatory for Amadeus.
</CarFeaturesRQ>

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