Vehicle Search by Vehicle Type

VehicleReqRsp.xsd
Vehicle Search
By default, a Vehicle Search response returns all available Vehicle types. However, the request can be modified to include vehicle type information such as vehicle categories, classes, door counts, and fuel types.
VehicleModifier attributes can be sent in combination with VehicleType values. Alternately, individual Vehicle modifiers can be requested using VehicleSearchModifiers/VehicleModifier. See Vehicle Search by Vehicle Modifiers for details.
Some providers also permit a combination of Vehicle Modifier attributes and Vehicle Types. See Exceptions for details.
Schema
See the following transactions for Vehicle Search:
How To
VehicleType is a modifier that can be added into the standard Vehicle Search request.
- Enter the minimum required search data for a Vehicle Search in VehicleSearchAvailabilityReq.
- Enter /VehicleSearchModifiers/VehicleType to specify the type of vehicles to include in the search.
- Industry-standard pseudo codes, which combine various types of vehicle modifiers, such as categories, classes, door counts, and fuel types. Pseudo vehicle codes are used as search qualifiers to enable easy retrieval of subsets of vehicles.
- Universal API enumerations of the pseudo codes.
-
Search with wild cards (pseudo codes) on Galileo or Apollo.
Galileo (1G) and Apollo (1V) support wild card requests using pseudo codes. The following matrix shows the codes used for the pseudo vehicle codes. The value of the characters is determined by their sequence within the four-character pseudo code.
Class/Size
(First Character)Category
(Second Character)Transmission/Drive
(Third Character)Fuel/Air Conditioning (AC)
(Fourth Character)M
Mini
B
2-3 door
M
Manual Unspecified Drive
R
Unspecified Fuel with AC
N
Mini Elite
C
2-door or 4-door
N
Manual Four-Wheel Drive
N
Unspecified Fuel without AC
E
Economy
D
4-5 door
C
Manual All-Wheel Drive
V
Petrol with AC
H
Economy Elite
E
Coupe
A
Automatic Unspecified Drive
Z
Petrol without AC
C
Compact
F
SUV
B
Automatic Four-Wheel Drive
D
Diesel with AC
D
Compact Elite
G
Crossover
D
Automatic All-Wheel Drive
Q
Diesel without AC
I
Intermediate
H
Motor Home
H
Hybrid with AC
J
Intermediate Elite
J
Open-Air All Terrain
I
Hybrid without AC
S
Standard
K
Commercial/Van Truck
E
Electric with AC
R
Standard Elite
L
Limousine
C
Electric without AC
F
Full Size
M
Monospace
L
LPG/Compressed Gas with AC
G
Fill-Size Elite
N
Roadster
S
LPG/Compressed Gas without AC
P
Premium
P
Pickup Regular Cab
A
Hydrogen with AC
U
Premium Elite
Q
Pickup Extended Cab
B
Hydrogen without AC
L
Luxury
R
Recreational Vehicle
M
Multi-Fuel with AC
W
Luxury elite
S
Sport
F
Multi-Fuel without AC
O
Oversize
T
Convertible
U
Ethanol with AC
X
Special
V
Passenger Van
X
Ethanol without AC
W
Wagon/Estate
X
Special
Y
Two-Wheel Vehicle
Z
Special Offer Car
Galileo and Apollo use the following rules to support wild cards in VehicleType for partially defined modifiers:
- Rule 1: If the first (Class) and/or second (Category) character is specified, the third (Transmission) character defaults to A (Automatic Unspecified Drive) and the fourth (Fuel/AC) character defaults to R (Unspecified Fuel with AC).
Scenarios:
- Only the first character is specified (for example, E): Search with E*AR
- Only the second character is specified (for example, C): Search with *CAR
- The first and second characters are both specified (for example, E and C): Search with ECAR
- Rule 2: If the third (Transmission) and/or fourth (Fuel/AC) character is specified, the first (Class) character defaults to E (Economy) and the second character (Category) defaults to C (2-door or 4-door).
Scenarios:
- Only the third character is specified (for example, A): Search with ECA*
- Only the fourth character is specified (for example, R): Search with EC*R
- The third and fourth characters both are specified (for example, A and R): Search with ECAR
- Rule 1 takes precedence in case of any other types of partial request.
Scenarios:
- The second (Category) and third (Transmission) characters are specified (for example, J and M). According to Rule 1, the first (Class) character defaults to the wild card and the fourth (Fuel/AC) character defaults to R: Search with *JMR
- The first (Class) and fourth (Fuel/AC) characters are specified (for example, H and P). According to Rule 1, the second (Category) character defaults to the wild card and the third character (Transmission) defaults to A: Search with H*AP
- A standard Vehicle Search response is returned. However, vehicle types are limited to those that meet the specified search parameters.
Two types of vehicle type data are accepted in Vehicle Type:
The vehicle types and number of types supported in a request varies by provider. Either the enumeration or pseudo code can be sent in VehicleType.
Vehicle Type code enumerations are returned in the response, even if pseudo codes were sent in the request.
Exceptions

- Both Vehicle Modifiers and Vehicle Types in the same request.
- A maximum of three Vehicle Modifiers or Vehicle Types (enumerated or pseudo codes) in the same request.
Vehicle Modifiers take precedence over Vehicle Types. If more than three modifiers/types are requested, the following warning is returned: First 3 car types considered in the request considering VehicleModifiers and VehicleTypes.A maximum of 3 car types are supported for the requested provider. Vehicle Modifier Types are processed first; any Vehicle Types are processed only if the maximum was not reached by the Vehicle Modifiers. - If VehicleSearchModifiers/VehicleModifier/Category is included in a request that also includes VehicleSearchModifiers/VehicleTypeonly Category is considered, and a warning is sent in the response.

Worldspan does not support combining Vehicle Modifiers and Vehicle Types (enumerated or pseudo code).
Worldspan supports only one Vehicle Type in a Vehicle Search request. If no VehicleModifier attributes are provided and multiple VehicleType attributes are provided, only the first VehicleType is considered, and a warning is sent in the response.
-
Worldspan supports max of 10 car types - actual or pseudo car types.
(Note - 1P has a functionality whereby agencies can create their own pseudo car codes, but this is not planned to be rolled out and waiting for a customer request as per Michael Loesch. Hence uAPI will not support such a future functionality)