Cartrawler OTA XML

CarTrawler OTA XML Interface
Version: 1.16
Date: 15/04/14

http://www.cartrawler.com

DO NOT DO BOOKINGS ON CARTRAWLER PRODUCTION SERVER WITHOUT
PRIOR PERMISSION

Copyright 2013 CarTrawler. All rights reserved. Page | 2

OTA Version ......................................................................................................................... 5
Messages .............................................................................................................................. 5
Mandatory fields / Maximum field lengths ........................................................................ 5
Example XML messages ..................................................................................................... 6
Support ................................................................................................................................. 6
Communication to our test Server ..................................................................................... 6
Client ID ................................................................................................................................ 6
Region Sensitive Searching ............................................................................................... 7
Important Fields ..................................................................................................................... 7
Transport .............................................................................................................................. 7
Data Compression ............................................................................................................... 7
Supported Currencies ......................................................................................................... 8
Sample Java Client .............................................................................................................. 9
Command lines arguments for sample java client. .................................................................... 9
Multi Language Support .................................................................................................... 10
Supported Languages can be found at: .......................................................................... 10
Static Files .......................................................................................................................... 11
ctlangauge ........................................................................................................................... 11
ctcurrency ............................................................................................................................ 11
isocountry............................................................................................................................. 11
ctlocation .............................................................................................................................. 12
Example Messages ............................................................................................................ 13
OTA_PingRQ ................................................................................................................................ 13
Important Fields ................................................................................................................... 13
OTA_VehLocSearchRQ (sample 1) ............................................................................................. 13
OTA_VehAvailRateRQ ................................................................................................................. 17
Note: ConsumerIP .................................................................................................................... 18
Header...................................................................................................................................... 18
VehAvailRSCore element ........................................................................................................ 19
VehVendorAvails element ........................................................................................................ 19
Pickup Types ....................................................................................................................... 20
VehAvail element ..................................................................................................................... 21
Explanation of Fee Purpose Codes ..................................................................................... 23
Special Offers ...................................................................................................................... 23
Discounted Price Offers ....................................................................................................... 24
Rate Qualifier / Rate Types ................................................................................................. 25
Payment Types .................................................................................................................... 25
Fuel Policy Information ........................................................................................................ 26
Supported Location Search Values ................................................................................. 34
Airport IATA Code .................................................................................................................... 36

PRIOR PERMISSION

Multiple Search ........................................................................................................................ 39
Advanced One-way Rental Searching ..................................................................................... 41
OTA_VehResRQ ................................................................................................................. 43
Important Fields ................................................................................................................. 44
Life Span for a quote ......................................................................................................... 45
Credit Card required for booking car .............................................................................. 45
PaymentCard CardCode attribute ....................................................................................... 46
PaymentCard CardType attribute ........................................................................................ 46
Credit Card ExpireDate ........................................................................................................ 46
Flight Information at Airports................................................................................................ 46
Test Credit Cards on OTATest ............................................................................................ 46
OTA_VehCancelRQ ........................................................................................................... 47
Example responses ............................................................................................................. 49
Example Response .............................................................................................................. 50
No Excess Insurance Quote ............................................................................................. 52
OTA_InsuranceQuoteRQ .................................................................................................. 52
OTA_InsuranceQuoteRS ............................................................................................................. 54
Insurance Display ......................................................................................................................... 55
Element Guide ......................................................................................................................... 57
Display Only Elements ......................................................................................................... 57
Booking No Excess Insurance ......................................................................................... 58
OTA_VehResRQ .......................................................................................................................... 59
Cancelling No Excess Insurance ..................................................................................... 61
Cartrawler Specific Messages .......................................................................................... 62
CT_VehCountrySearchRQ ........................................................................................................... 62
CT_VehLocSearchRQ (Pickup locations, Verbose) ..................................................................... 63
CT_VehLocSearchRQ (Pickup locations, Compact) ...................................................... 65
CT_VehLocSearchRQ (Return locations, Verbose) ....................................................... 67
CT_VehLocSearchRQ (Return locations, Compact) .................................................................... 68
CT_FleetRQ ........................................................................................................................ 71
Example SIPP code returned in OTA_VehAvailRS message ........................................ 71
Example Response ............................................................................................................ 72
Country wide CT_FleetRQ ................................................................................................ 73
CT_SpecialOffersRQ ......................................................................................................... 74

PRIOR PERMISSION

Feed URL Format ............................................................................................................... 74
Example A: ......................................................................................................................... 74
Example B: ......................................................................................................................... 74
Important ............................................................................................................................ 74
Sample Booking ................................................................................................................. 76
Use OTA_VehLocSearchRQ to Search for Location ...................................................... 76
Location Response .................................................................................................................. 76
Vehicle Avail Response .................................................................................................... 80
Use OTA_VehResRQ to Make a Reservation .................................................................. 82
Vehicle Reservation Response ................................................................................................ 83
Requesting Special Equipment ........................................................................................ 85
Special Equipment availability ......................................................................................... 85
Requesting Special Equipment ........................................................................................ 87
Appendix B ......................................................................................................................... 88
Common Error conditions ................................................................................................ 88
Appendix C ......................................................................................................................... 91
Certification Process ......................................................................................................... 91
The typical Certification process will include ................................................................. 91
NOTE : ONLY BOOK 1 CAR FOR EACH TEST. ............................................................... 91
Booking Prepaid / Partpaid reservation .......................................................................... 92
Booking prepaid/partpaid reservation ............................................................................. 92

DO NOT DO BOOKINGS ON CARTRAWLER PRODUCTION SERVER
WITHOUT PRIOR PERMISSION

OTA Version
Supported OTA Version: 2009A
Messages
Messages Support;
OTA_PingRQ.xsd
OTA_PingRS.xsd
OTA_VehLocSearchRQ.xsd
OTA_VehLocSearchRS.xsd
OTA_VehLocDetailRQ.xsd
OTA_VehLocDetailRS.xsd
OTA_VehAvailRateRQ.xsd
OTA_VehAvailRateRS.xsd
OTA_VehResRQ.xsd
OTA_VehResRS.xsd
OTA_ErrorRS.xsd

OTA Document containing information about the messages and the OTA Schemas
can be found and downloaded from;
http://www.opentravel.org

The Messages are stateless. No Session is created.
Mandatory fields / Maximum field lengths
All incoming messages are validated against the OTA Schemas.
This defines mandatory fields, and min/max values of these fields.

One of the most common errors with the OTA Schema is to provide an empty
element.
e.g. the following element would cause a Schema error
<element name=fred age=/>

but the following would be valid
<element name=fred/>

Typically with the OTA Schemas, passing an empty attribute will be invalid, but the
attribute itself will be optional.

A typical error when the XML is invalid could look like:
"Value '' is not facet-valid with respect to pattern '[0-9A-Z]{1



Example XML messages
We only support a subset of the OTA defined messages.
The XML examples in this document were designed to highlight the important fields
upon which we rely on.
Support
If you have any questions or technical problems regarding Cartrawler OTA XML
Interface use the support web page at;

https://partners.cartrawler.com/

Communication to our test Server

IP : otatest.cartrawler.com
Port : 20002

The service is available at;
http://otatest.cartrawler.com:20002/cartrawlerota

The service is also available over https at;
https://otatest.cartrawler.com:20000/cartrawlerota

Client ID
Every message you send the OTA Servers must contain your Client ID
This is passed in every message in the POS element.

The ID with ID_Context CARTRAWLER should contain your client ID.

<Pos>
<Source ISOCurrency="EUR">
<RequestorID Type="16" ID="999999" ID_Context="CARTRAWLER" />
</Source>
</Pos>



Region Sensitive Searching
The region and residency of the end user can be passed in all requests within the
first Source element. This enables more accurate content searching.

<Pos>
<Source ISOCurrency="EUR" ISOCountry="IE" TerminalID="US">
</Source>
</Pos>

Example above describes a request from a customer who is a resident in Ireland but
is searching from a computer in America.

Important Fields
ISOCountry ISO 2-digit country code of the customers
country of residence.
TerminalID ISO 2-digit country code of the customers
current location.

Transport
As per OTA Transport Protocol Reference HTTPV1.0, the transport protocol is based
on a simple HTTP POST transaction.

NOTE: Our OTA Server is not implemented as a Web Service. There are no
WDSL files.

To access
On receiving an XML request, the request is processed, and an XML response is
returned.

Data Compression
All requests to CarTrawler should be gzip compression enabled. If gzip is enabled by
the client we will respond with a gzipped response. Enabling gzip increases the
speed at which messages are transferred and also reduces the bandwidth usage.
We would encourage all clients to enable this.

Client ID
Every message you send the OTA Servers must contain your Client ID
This is passed in every message in the POS element.
<POS>
</Source>
</Pos>


Most messages have a POS section that contains a RequestID tag with an ID
element.
This ID code must be generated by Car Trawler and supplied to you for use in
your messages.

Attribute ID for RequestorID element. The unique id code which identifies you
(supplied by cartrawler.com).
Optional attribute ISOCurrency in
Source Element.
If supplied then all amounts returned in
the response will be converted to this
currency.
By default all amounts will be returned in
the currency GBP.
Supported Currencies
The list of supported currencies can be found at:
https://otageo.cartrawler.com/cartrawlerota/files/static/ctcurrency.xml

Note: The list of supported currencies can change at any time.


Sample Java Client
A sample Java Client is supplied which can be used to demonstrate the Car Trawler
OTA XML Interface.
A compiled version of the client is supplied in the jar file
CartrawlerOTAXMLClient.jar.

Note: It Requires Java 1.5 to run.

Below is a sample command line to run the client.

C:\projects\cartrawlerota\build>java -jar CartrawlerOTAXMLClient.jar
--server=http://otatest.cartrawler.com:20002/cartrawlerota
--output=output OTA_PingRQ.xml

This client requires you to install the security certificate for Java.
Command lines arguments for sample java client.
usage: java Http --server=<url> [--output=<fileprefix>] [<files>...]
--server=<url> The http or https url of the server to connect too.
--output=<fileprefix>
A sequence number is appended to fileprefix and the response is
output to this file. Existing files will be overwritten. Use '-' or no
option if the response should be output to standard output.
<files> A list of input filenames which should be sent to the server. Use '-'
or an empty list the input is from standard input.



Multi Language Support

Some messages can return data in several languages.
The PrimaryLangID attribute is used to specify what language you want the
response to be in.
If the language specified is not supported, the response will be returned in English.
If no language is specified, the response will be returned in English.
e.g.
<OTA_VehAvailRateRQ
xmlns="http://www.opentravel.org/OTA/2003/05"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05
OTA_VehAvailRateRQ.xsd"
Target="Test"
Version="1.005"
PrimaryLangID="PL">

All message support the PrimaryLangID attribute.
Supported Languages can be found at:
https://otageo.cartrawler.com/cartrawlerota/files/static/ctlanguage.xml
e.g.
Language Language Code Example
English EN PrimaryLangID=EN
French FR PrimaryLangID=FR
Polish PL PrimaryLangID=PL
Italian IT PrimaryLangID=IT

A language code can also be supplied in the format XX-XX.
In this case only use the code before the - separator.
i.e. The following codes are all valid and will be treated as English;
en English
en-us English (United States)
en-gb English (United Kingdom)
en-au English (Australia)
en-ca English (Canada)
en-nz English (New Zealand)
en-ie English (Ireland)
en-za English (South Africa)
en-jm English (Jamaica)
en English (Caribbean)
en-bz English (Belize)
en-tt English (Trinidad)



Static Files

We provide several static files from the OTA Servers, some of which are available in
multiple languages.

Single Static files.
There are only version of these files which include:

ctlangauge
https://otageo.cartrawler.com/cartrawlerota/files/static/ctlanguage.xml
Contains list of languages supported.

ctcurrency
https://otageo.cartrawler.com/cartrawlerota/files/static/ctcurrency.xml
Contains list of currencies supported.

Multi lingual Static files.
These files are available in all the languages which we support.

isocountry
This provides a list of countries and country codes in our supported languages.
e.g.
https://otageo.cartrawler.com/cartrawlerota/files/static/isocountry.EN.xml
https://otageo.cartrawler.com/cartrawlerota/files/static/isocountry.PL.xml
https://otageo.cartrawler.com/cartrawlerota/files/static/isocountry.ES.xml

Sample xml
<?xml version="1.0" encoding="UTF-8" ?>
<ISOCountries xmlns="http://www.cartrawler.com/">
<ISOCountry CountryCode="IE" DiallingCode="353">Ireland</ISOCountry>

<ISOCountry CountryCode="QA" DiallingCode="974">Qatar</ISOCountry>
</ISOCountries>



ctlocation
This provides a list of all our locations with our Cartrawler location ID and Airport
IATA codes (for airport locations)
e.g.
https://otageo.cartrawler.com/cartrawlerota/files/static/ctlocation.EN.xml
https://otageo.cartrawler.com/cartrawlerota/files/static/ctlocation.FR.xml
https://otageo.cartrawler.com/cartrawlerota/files/static/ctlocation.DE.xml

Sample xml
<CTLocations xmlns="http://www.cartrawler.com/">
<Country code="AL" name="Albania" continent="Europe">
<Location Id="7188" Name="Tirana Airport"
Lat="41.42108838" Lng="19.71271276"
Address="Tirana Airport, Muhamet Gjollesha Str., Tirana"
CityName="Tirana" CountryCode="AL" Airport="1"
AirportCode="TIA" RailwayStation="0"/>
...
</Country>

otacodetable
This provides a list of ota codes in our supported languages.
e.g.
https://otageo.cartrawler.com/cartrawlerota/files/static/otacodetable.EN.xml
https://otageo.cartrawler.com/cartrawlerota/files/static/otacodetable.FR.xml
https://otageo.cartrawler.com/cartrawlerota/files/static/otacodetable.DE.xml

Sample xml
<OTACodeTables xmlns="http://www.cartrawler.com/">
<OTACodeTable NameCode="EQP">
<Code Value="28" Name="Wheelchair accessible van" />

<Code Value="8" Name="Child toddler seat" />
</OTACodeTable>
<OTACodeTable NameCode="VEC">
<Code Value="3" Name="SUV" />

<Code Value="12" Name="Recreational" />
</OTACodeTable>
</OTACodeTables>



Example Messages
OTA_PingRQ
<OTA_PingRQ
xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_PingRQ.xsd"
Target="Test"
Version="1.003">
<EchoData>Are you there</EchoData>
</OTA_PingRQ>
Important Fields
Attribute Version for OTA_PingRQ
element.
This must be 1.003
EchoData element. Contains text which will be returned to
you.
OTA_VehLocSearchRQ (sample 1)
<?xml version="1.0" encoding="UTF-8"?>
<OTA_VehLocSearchRQ
OTA_VehLocSearchRQ.xsd"
Version="1.005"
PrimaryLangID="en"
Target="Test">
<POS>
<Source>
</Source>
</POS>
<VehLocSearchCriterion ExactMatch="true" ImportanceType="Mandatory">
<Address>
<CityName>London</CityName>
<CountryName Code="GB" />
</Address>
</VehLocSearchCriterion>
</OTA_VehLocSearchRQ>
Important Fields
Field Description
Attribute Version for
OTA_VehLocSearchRQ element.
This must be 1.005
Attribute Code for CountryName
element.
The country code you wish search on.
Element CityName. Optional Cityname that can be used to
narrow the Search.


<OTA_VehLocSearchRQ
Version="1.005"
Target="Test">
<POS>
<Source>
</Source>
</POS>
<RefPoint>LGW</RefPoint>
Important Fields
Field Description
Element RefPoint. This is a IATA airport code. The
search will return locations at the
specified airport.

<OTA_VehLocSearchRQ
Version="1.005"
Target="Test">
<POS>
<Source>
</Source>
</POS>
<Position Latitude="53.35" Longitude="-6.23" />
<Radius Distance="10" DistanceMeasure="km" />
Important Fields
Field Description
Attribute 'Latitude' and 'Longitude' of
'Position' element.
The Latitude and Longitude in decimal
degrees which is used as the centre point
of the location search.
Attribute 'Distance' and
'DistanceMeasure' of 'Radius' element.
Return any locations that are within the
given 'Distance' of centre point. The
supported units for 'DistanceMeasure'
are 'km', 'kilometre', or 'mile'.

Note :
It is possible for a Location Search to return a result set that is to large.
The OTA specifications will only allow the search to return 100 records.


If the search returns more than 100 records, then the error message Search Criteria
Invalid error code 161 will be returned.
Use the CT_VehLocSearchRQ if you need to get around the maximum number of
records restriction.


OTA_VehLocDetailRQ
<OTA_VehLocDetailRQ
OTA_VehLocDetailRQ.xsd"
Version="1.005">
<POS>
<Source>
</Source>
</POS>
<Location CodeContext="CARTRAWLER" LocationCode="71"/>
</OTA_VehLocDetailRQ>
Important Fields
Field Description
OTA_VehLocDetailRQ element.
This must be 1.005
Attribute LocationCode for Location
element.
The unique location code you wish extra
information about. This is returned in the
OTA_VehLocSearshRS message.



OTA_VehAvailRateRQ

This message is used to request car availability from a single Location.

<OTA_VehAvailRateRQ
Target="Test"
Version="1.005">
<POS>
</Source>
</POS>
<VehAvailRQCore Status="Available">
<VehRentalCore PickUpDateTime="2009-04-01T07:00:00"
ReturnDateTime="2009-04-09T19:00:00">
<PickUpLocation CodeContext="CARTRAWLER" LocationCode="71" />
<ReturnLocation CodeContext="CARTRAWLER" LocationCode="71" />
</VehRentalCore>
<DriverType Age='30'/>
</VehAvailRQCore>
<VehAvailRQInfo PassengerQty='3'>
<Customer>
<Primary>
<CitizenCountryName Code='IE' />
</Primary>
</Customer>
<TPA_Extensions>
<ConsumerIP>182.456.432.123</ConsumerIP>
</TPA_Extensions>
</VehAvailRQInfo>
</OTA_VehAvailRateRQ>
Important Fields
Field Description
OTA_VehAvailRateRQ element.
This must be 1.005
Attribute ISOCurrency for Source
element.
The Currency that amounts will be
displayed in the response.
Attribute LocationCode for
PickUpLocation and ReturnLocation
elements.
The unique location code you wish
availability returned from. This is
returned in the OTA_VehLocSearchRS
message.
Attribute PickupDateTime for element
VehRentalCore
The Date & Time you wish to pickup the
Vehicle
Attribute ReturnDateTime for element
VehRentalCore
The Date & Time you wish to return the
Vehicle
Attribute Age for DriverType element This is mandatory.
You need to supply the drivers age in this
field.
This will affect what cars are available,


and the price of the cars.
Attribute PassengerQty for
VehAvailRQInfo element.
This is the preferred passenger quantity
for the car based on the number of
passengers. The value should not
include the driver.
Attribute Code for CitizenCountryName
element.
This is mandatory.
This is the country code for the drivers
This is required as different rates may be
available depending on it.
Element ConsumerIP in
TPA_Extensions element.
This is mandatory.
This is the IP address of your consumers
machine.

Note: ConsumerIP
It is a mandatory requirement that the consumers IP is included in the
OTA_VehAvailRateRQ message. The Consumer IP is required so that our system is
protected from abusive traffic. Failure to include this information will result in an error.

The preferred Size of the car is taken from the OTA Code List table.
Examples of ones commonly used are;

Size Description
1 Mini
3 Economy
4 Compact
6 Intermediate
7 Standard
8 Fullsize
9 Luxury
10 Premium
11 Minivan
12 12 passenger van
24 Exotic

OTA_VehAvailRateRS overview
All OTA_VehAvailRateRS have the same format, no matter what flavour of the
request message is used (single, multi, iata).

The message is large. For documentation purposes it is broken down into its
component parts.

Header

<OTA_VehAvailRateRS xmlns="http://www.opentravel.org/OTA/2003/05"
xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05" Version="2.004"
Target="Production" PrimaryLangID="EN" TimeStamp="2009-11-07T17:23:24.494Z">
<Success/>



Important Fields
Field Description
Success If present, then availability was
successful

VehAvailRSCore element
<VehAvailRSCore>
<VehRentalCore PickUpDateTime="2007-12-17T20:00:00Z" ReturnDateTime="2007-12-
20T06:00:00Z">
<PickUpLocation CodeContext="CARTRAWLER" LocationCode="338" Name="Orlando Airport
(MCO)"/>
<ReturnLocation CodeContext="CARTRAWLER" LocationCode="338" Name="Orlando Airport
(MCO)"/>
</VehRentalCore>

Important Fields
Field Description
Attribute PickUpDateTime of
VehRentalCore element
The pickup date & time
Attribute ReturnDateTime of
VehRentalCore element
The return date & time
Attribute LocationCode & Name of
PickupLocation element
The Cartrawler location code and
location name for the pickup location.
Attribute LocationCode & Name of
ReturnLocation element
The Cartrawler location code and
location name for the return location.

VehVendorAvails element
<VehVendorAvails>
<VehVendorAvail>
<Vendor Code="3" CodeContext="CARTRAWLER"/>
<VehAvails>

<VehAvail>

</VehAvail>

</VehAvails>
<Info>
<LocationDetails AtAirport="1" Code="11" Name=" Dublin - Airport">
<Address Remark="53.4260000,-6.2390000">
<AddressLine> Dublin Airport Arrivals Hall , Dublin</AddressLine>
<CountryName Code="IE"/>
</Address>
<Telephone PhoneNumber=" +353 1 60511111"/>
<AdditionalInfo>
<CounterLocation Location="VWF_1.VWF.X">
</AdditionalInfo>
</LocationDetails>
</Info>
</VehVendorAvail>

<VehVendorAvail>


</VehVendorAvail>

</VehVendorAvails>
The availability response is broken down by vendor (car supplier).
The response can contain multiple VehVendorAvail elements, one for each vendor.
Each VehVendorAvail element contains 3 elements;

Vendor element Contains Cartrawler unique code for the
car vendor.
VehAvails Contains multiple VehAvail elements
(which contain available cars).
Info Contains vendor specific location
address information.
Each vendor at a single location can
have their own unique location address.
For one-way rentals the Info element
would contain 2 LocationDetails
elements. Otherwise only 1 is returned.
The code attribute for the LocationDetail
element matches the Cartrawler location
code for this location.

Pickup Types
Rentals agents can support various location types. The location type of the agent is
detailed in the CounterLocation element.

<LocationDetails AtAirport="1" Code="11" Name=" Dublin - Airport">
...
<AdditionalInfo>
<CounterLocation Location="VWF_1.VWF.X">
</AdditionalInfo>
...
</LocationDetails>

The 'Type' could be one of the following:

Type Description
VWF_1.VWF.X Terminal Counter And Car
VWF_2.VWF.X Shuttle To Counter And Car
VWF_3.VWF.X Terminal Counter Shuttle To Car
VWF_4.VWF.X Meet And Greet
VWF_5.VWF.X Unknown
VWF_6.VWF.X Car And Driver



VehAvail element
This is the heart of the availability message.
Each VehAvail element corresponds to an available car.
<VehAvail>
<VehAvailCore Status="Available">
<Vehicle AirConditionInd="true" TransmissionType="Automatic" FuelType="Unspecified"
DriveType="Unspecified" PassengerQuantity="" BaggageQuantity="4" Code="CDAR"
CodeContext="CARTRAWLER">
<VehType VehicleCategory="1" DoorCount="4-5"/>
<VehClass Size="4"/>
<VehMakeModel Name="Chevrolet Cavalier Automatic 4dr or similar" Code="CDAR"/>
<PictureURL>https://www.cartrawler.com/otaimages/chevrolet/cavalier.jpeg
</PictureURL>
<VehIdentity VehicleAssetNumber="22033"/>
</Vehicle>
<RentalRate>
<RateQualifier RateQualifier="PREPAID-IN" />
</RentalRate>
<TotalCharge RateTotalAmount="151.48" EstimatedTotalAmount="151.48"
CurrencyCode="AUD"/>
<PricedEquips>
<PricedEquip>
<Equipment EquipType="4">
<Description>Ski rack</Description>
</Equipment>
<Charge Amount="24.02" CurrencyCode="AUD" TaxInclusive="true"
IncludedInRate="false"/>
</PricedEquip>
<PricedEquip>
<Description>Infant child seat</Description>
</Equipment>
<Charge Amount="22.39" CurrencyCode="AUD" TaxInclusive="true"
IncludedInRate="false"/>
</PricedEquip>
</PricedEquips>
<Fees>
<Fee Amount="26.59" CurrencyCode="AUD" Purpose="22"/>
<Fee Amount="117.00" CurrencyCode="USD" Purpose="23"/>
<Fee Amount="0.00" CurrencyCode="AUD" Purpose="26"/>
</Fees>
<Reference Type="16" ID="338:99:D" ID_Context="CARTRAWLER" DateTime="2007-11-
07T17:23:24.494Z"
URL="CT#S4eFa7iALKbyz3A4mLLp%2F1Bbr3ViOPNYwMOEhS7Mu8mo8Zx%2BbNazn4qirPqn6jhdnHc0EANEIG
kK%0A8l3RQUCKzl%2BgEcnwBjcQ1VLHfOM9LDUXML8qMvT8DmdNzkRQuIKtIPOzAZRG3LMoj8hrZk5lDLZ0%0A
Z0USLo1Bi%2BFRz7JAHXq1j76gpGR9Xj9YAbujnEQqPYXgiQJb2ATdunfJrz9LlIKOZkux0g2uuYRt%0As6fX5
pBefuunACABisdu7N7lIak4vFl2RfSAxgfV50WhMv0DKpYjJLt7CnMNi8AVta8DCB8Uno6E%0ARBQp3A%3D%3D
"/>
<TPA_Extensions>
<Config OrderBy="88" Insurance="false" Duration="3" Limited=1 BestPrice="1"
CC_Info="true"/>
<OrderBy Index="88" />
<Duration Days="3"/>
<Fees>
</Fees>
<CC_Info Required="true" />
<SpecialOffers>
<Offer Type="Two free upgrades" ShortText="Free upgrade to Vauxhall Astra or
Similar.">Free upgrade from Toyota Yaris to Vauxhall Astra or Similar</Offer>
</SpecialOffers>
<CurrencyExchange Rate="0.94"/>
</TPA_Extensions>
</VehAvailCore>
</VehAvail>



Important Fields
Field Description
RateQualifer attribute for RateQualifier
element.
This element & attribute describe which
type of Rate.
This describes the payment type,
weather this is prepaid, postpaid or
partpaid.
A section below will describe this in
detail.
Fee element with a Purpose attribute of
22.
22 is the OTA Code for Prepay
amount.
This is the estimated deposit fee that will
be taken from the customer if they book
this vehicle.
23
This is the amount the customer will pay
to the Car Vendor when collecting the
vehicle.
Reference field with all attributes. The Reference field uniquely identifies
the car along with the supplied Rate.
Use this value to book the car using the
OTA_VehRes message.
OrderBy attribute of Config element This is the orderby id for the car.
Each Car returned as an ordered id
assigned to it.
We suggest you display the cars in the
order of this number.
Duration attribute of Config element The duration in days of the rental.
This is useful if different pickup and
return times are used.
Attribute BestPrice of Config element When this attribute is present, then this
car is flagged as having our lowest price
at this location.
This attribute is optional.
Attribute Limited of Config element When this attribute is present, then this
car is flagged as having low availability.
This attribute is optional.
Attribute CC_Info of Config element When the CC_Info attribute is true then
a credit card will be required to book this
car. When it is false then no credit card
will be required.
SpecialOffers element This contains a list of Special Offers in
Offer elements.
The Type attribute is a free text
description of the type of Special offer.
The text in the Offer element is
translated to the requested language.
Fee in TPA Extension element The Fees in the OTA defined Fees
section are returned in the currency
requested in the response.


This is the deposit amount 22 in the
currency which we will charge the
customers credit card (not the currency
the customer requested).
This is only present if we are charging in
a different currency to the requested
currency.
Rate element of CurrencyExchange
element.
Linked with the Fee above.
This is the currency exhange rate
between the currency we charge our
deposit in, and the currency the customer
requested.

Explanation of Fee Purpose Codes
Purpose Code Description
6 Cartrawler Booking Fee
22 Deposit Fee (Amount taken from customer s credit card when
they confirm the booking, includes Cartrawler Booking Fee).
23 Fee to pay on arrival (Amount customer will pay supplier on
collection of car).

The EstimatedTotalAmount is equal to the RateTotalAmount plus the Cartrawler
Booking Fee (Purpose Code 6).
The Fees are for information purpose only.
They do not need to added to the amounts.

Note: All other fees returned in the XML should be ignored.

Special Offers
Some cars can have Special Offers associated with them.
Examples of Special Offers include, free upgrades, free petrol.
These cars will contain a SpecialOffers element in the TPA_Extensions element for
the VehAvailCore. Offers are applied to the cars on the CarTrawler side so this
element is only used for customer display purposes.
e.g.
<TPA_Extensions>
<SpecialOffers>
<Offer Type="free_additional_driver">Free additional driver</Offer>
</SpecialOffers>
</TPA_Extensions>

Important Fields
Field Description
Type Fixed string value representing offer type
Text Human readable description of offer



Offer Types Description
monetary_discount Used to indicate a discounted price
free_gps
percentage_discount Used to indicate a discounted price
free_additional_driver
free_fuel
free_days
free_winter_carkit
free_congestion_charge
free_child_seat
free_personal_ainsurance
euro_disney_pass
free_ski_pass
free_upgrade
percentage_discount_gps
free_wifi
guaranteed_mam
generic_offer

Discounted Price Offers
e.g.
<VehAvail xmlns="http://www.opentravel.org/OTA/2003/05">
<VehAvailCore Status="Unavailable">
...
CurrencyCode="EUR"/>
<Reference .../>
<TPA_Extensions>
<SpecialOffers>
<Offer Type="monetary_discount" Discount="20.00" Amount="120.00"
CurrencyCode="EUR">Monetary Discount</Offer>
</SpecialOffers>
</TPA_Extensions>
</VehAvailCore>
...
</VehAvail>

Important Fields
Field Description
Type Fixed string value representing offer type
Discount Amount of discount applied, if offer type is percentage_discount
this value is a percentage unit type.
Amount Original Amount of vehicle before discount applied
CurrencyCode Currency value
Text Human readable description of offer



Rate Qualifier / Rate Types

The RateQualifer element describes the type of Rate associated with the vehicle.
This includes the payment type,
whether or not the rate is an exclusive or inclusive product,
and any promotions associated with the rate.

Example Rate Qualifer

<RentalRate>
<RateQualifier RateQualifier="PREPAID-IN" PromotionCode="DIAMOND"/>
</RentalRate>

The 'RateQualifer' contains a 'RateQualifier' attribute and a optional
'PromotionCode' attribute.

The 'RateQualifier' could be one of the following:

RateQualifier attribute Description
PREPAID-IN Fully Prepaid, Inclusive product
PREPAID-EX Fully-prepaid, Exclusive product
POSTPAID-IN Fully-postpaid, Inclusive product
POSTPAID-EX Fully-postpaid, Exclusive product
PARTPAID-IN Partpaid (deposit), Inclusive product
PARTPAID-EX Partpaid (deposit), Exclusive product

Payment Types
PREPAID means the full cost is paid up front (though some fees may be paid on
arrival).
POSTPAID means the full cost is paid when picking up the car (no deposit).
PARTPAID means a deposit is paid up front, with the remainder being paid when
pickup up the car.



PromotionCode
The 'PromotionCode' attribute is optional, and can be one of the follow:
GOLD
PLATINUM
DIAMOND
INCLUSIVE_NO_EXCESS
INCLUSIVE_WITH_GPS

It is possible to receive several rates for the same car from the same supplier, if this
is the case they will appear as different VehAvail elements.
These cars will have different costs, and have different Rental Conditions.

The list of unique rate types are:

Rate Type RateQualifier
attribute
PromotionCode attribute
Basic Ends with -EX None
Inclusive Ends with -IN None
Gold Ends with -IN GOLD
Platinum Ends with -IN PLATINUM
Diamond Ends with -IN DIAMOND
Inclusive no
excess
Ends with -IN INCLUSIVE_NO_EXCESS
Inclusive with GPS Ends with -IN INCLUSIVE_WITH_GPS
Note: New Promotion codes might be added in the future.

Fuel Policy Information
...
<Reference..../>
<TPA_Extensions>
<FuelPolicy Type="EMPTYEMPTY" Description="Empty Return Empty"/>
...
<TPA_Extensions>
...
When available the fuel policy of the rental will be returned in the TPA_Extensions
element of the VehAvailCore element.

The FuelPolicy could be one of the following:

Type attribute Description
FULLFULL Full Return Full
EMPTYEMPTY Empty Return Empty
FULLEMPTY Full Return Empty
HALFEMPTY Half Full Return Empty
QUARTEREMPTY Quarter Full Return Empty
HALFHALF Half Full Return Half Empty
QUARTERQUARTER Quarter Full Return Quarter Full
UNKNOWN See Rental Conditions



Credit Card required for booking car
Some cars require a Credit Card in order to book them, and some do not.
Each car returned in the availability response has a flag which indicates if this is
required.

<TPA_Extensions>

<CC_Info Required="true"/>

</TPA_Extensions>

The CC_Info Required attribute is true when a credit card is required to book the
car, and is false otherwise.

When a credit card is required, the reservation message OTA_VehResRQ must
contain valid credit card information in a RentalPaymentPref element.

If no credit card is required, the reservation message must contain no
RentalPaymentPref element.

A credit card may be required in order to pay for the car (all or part payment),
or it may be required to hold the reservation for certain car suppliers.



Fee Breakdown
The Fee Breakdown is returned in the availability response in the
OTA_VehAvailRateRS message.

The Fee Breakdown is for display purposes only.
No calculations should be done using the information returned within the Fee
Breakdown.

All the individual Fee Breakdown elements are included in the Price of the car.
Some Fees might contain no amounts in them, some Fees might contain zero
amounts, and some Fees will contain non-zero amounts.

Some attributes returned in the Fee Breakdown are not documented, and should be
ignored.

The Fee Breakdown is returned back in the VehicleCharges and PricedCoverages
elements.
The PricedCoverages contain Insurance type products that are associated with the
car.

The VehicleCharges is made up of a list of VehicleCharge elements.
The PricedCoverages is made up of a list of PricedCoverage elements.



VehicleCharge element

The Vehicle charge element has the followings attributes:
Attribute name Mandatory/
Optional
Description
Description Mandatory A text description of the Fee (in the
language specified in the availability
request).
Amount Optional The cost of this fee.
CurrencyCode Optional The currency of the fee.
Purpose Mandatory A unique code for this Vehicle Charge.
We do not document what these codes
stand for.

E.g. Unlimited Mileage

...
<RentalRate>
<VehicleCharges>
<VehicleCharge Description="Breakdown assistance" TaxInclusive="true"
IncludedInRate="true" Purpose="602.VCP.X"/>
<VehicleCharge Description="Tax" IncludedInRate="true" Purpose="7"/>
<VehicleCharge Description="Unlimited mileage" TaxInclusive="true"
<VehicleCharge Description="Airport fee" Amount="0.00" CurrencyCode="EUR"
TaxInclusive="true" IncludedInRate="true" Purpose="30"/>
</VehicleCharges>
<RateQualifier RateQualifier="PREPAID-IN"/>
</RentalRate>
...

E.g. Limited Mileage

...
<RentalRate>
<RateDistance DistUnitName="Km" Quantity="100.0" Unlimited="false"
VehiclePeriodUnitName="Day"/>
<VehicleCharges>
<VehicleCharge Description="Airport fee" TaxInclusive="true" IncludedInRate="true"
Purpose="30"/>
</VehicleCharges>
<RateQualifier RateQualifier="PREPAID-IN"/>
</RentalRate>
...

If mileage information is available it will be returned in the response. When the
mileage is limited and the limit information is known it will be returned using the
RateDistance element.



RateDistance element

Optional
Description
DistUnitName Optional Unit for quantity value, supported values:
- Km
- Mile
Quantity Optional Distance included in limit
Unlimited Mandatory True, False value
VehiclePeriodUnitName Optional Period type unit code, supported values:
- Day
- Month
- RentalPeriod

PricedCoverage element
The Priced Coverage element has the following attributes:

Optional
Description
Charge
Description
Mandatory A text description of the Fee (in the language
specified in the availability request).
Charge Amount Optional The cost of this fee.
Charge
CurrencyCode
Optional The currency of the fee.
Coverage
CoverageType
Mandatory A unique code for this Vehicle Charge.
We do not document what these codes stand for.

e.g.
<PricedCoverages>
<PricedCoverage>
<Coverage CoverageType="6"/>
<Charge Description="Collision damage waiver (CDW)" Amount="0.00"
CurrencyCode="EUR" TaxInclusive="true" IncludedInRate="true"/>
</PricedCoverage>
<PricedCoverage>
<Charge Description="Theft waiver (TW)" Amount="0.00" CurrencyCode="EUR"
TaxInclusive="true" IncludedInRate="true"/>
</PricedCoverage>
<PricedCoverage>
<Charge Description="Third party liability protection (TP)" Amount="0.00"
CurrencyCode="EUR" TaxInclusive="true" IncludedInRate="true"/>
</PricedCoverage>
</PricedCoverages>



Collision Damage Waiver (CDW), CoverageType 6
If the excess amount is known for the CDW cover it will be returned in the response.
The excess information is returned in the Deductible element of the PricedCoverage.

...
<PricedCoverage>
<Charge Description="Collision damage waiver (CDW)" TaxInclusive="true"
IncludedInRate="true"/>
<Deductible Amount="1000.00" CurrencyCode="JPY"/>
</PricedCoverage>
...

Note: If no excess information is returned it does not imply that the policy has no
excess payable in the event of a claim.

Fee Breakdown Total
Fee Breakdown if available will be include in the VehAvail TPA_Extenstion element
of the OTA_VehAvailRateRS message in the Charge currency for the Vehicle. The
fee breakdown total is a sum of all of the fees that are included in the total rental
price and those that are available to CarTrawler from the VehicleCharges and
PricedCoverage elements.

e.g.

<TPA_Extensions>
...
<Fees>
<Fee Amount="17.87" CurrencyCode="USD" Purpose="104.FEE"/>
</Fees>
<CurrencyExchange Rate="1.641875" Rate23="0.609060"/>
...
</TPA_Extensions>


Example 1: Availability for car in Europe, for a European resident.

Vehicle Charges & PricedCoverages
<VehicleCharges>
<VehicleCharge Description="Airport fee" TaxInclusive="true" IncludedInRate="true"
Purpose="30"/>
<VehicleCharge Description="Unlimited mileage" TaxInclusive="true"
<VehicleCharge Description="Placement fee" TaxInclusive="true"
IncludedInRate="false" IncludedInEstTotalInd="true" Purpose="702.VCP.X"/>
</VehicleCharges>
...

...
<PricedCoverages>
<PricedCoverage>
<Charge Description="Collision damage waiver (CDW)" TaxInclusive="true"
</PricedCoverage>
<PricedCoverage>
<Charge Description="Third party liability protection (TP)" TaxInclusive="true"
</PricedCoverage>
<PricedCoverage>
<Charge Description="Theft waiver (TW)" TaxInclusive="true"
</PricedCoverage>
</PricedCoverages>

Fee Breakdown Display



Example 2: Availability for car in USA, for a USA resident.

Vehicle Charges & PricedCoverages
<VehicleCharges>
<VehicleCharge Description="LateCharge" Amount="0.00" CurrencyCode="EUR"
TaxInclusive="false" IncludedInRate="true" Purpose="1.RAW.X"/>
<VehicleCharge Description="Surcharge" Amount="10.31" CurrencyCode="EUR"
<VehicleCharge Description="APO CONCESSION" Amount="7.95" CurrencyCode="EUR"
<VehicleCharge Description="STATE SALES TAX" Amount="6.61" CurrencyCode="EUR"
<VehicleCharge Description="VEHICLE LIC FEE" Amount="6.72" CurrencyCode="EUR"
</VehicleCharges>

Fee Breakdown Display



Supported Location Search Values

The OTA_VehAvailRateRQ supports several location search values:

CarTrawler Specific Identifier
Airport IATA Code
GEO Point
Car Agent Identifier
Multiple Search (to be phased out, replaced by GEO Point)

Note: The OTA_VehAvailRate response will include the CarTrawler Location
Identifier. You must use this identifier when making further request such as
OTA_VehRes, CT_RentalConditions, etc...



CarTrawler Location Identifier

Full list of supported identifiers is available in the ctlocation.EN.xml feed. This search
type supports one-way rental searching.

<OTA_VehAvailRateRQ
xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_VehAvailRateRQ.xsd"
Target="Test"
Version="1.005">
...
<PickUpLocation CodeContext="CARTRAWLER" LocationCode="11"/>
<ReturnLocation CodeContext="CARTRAWLER" LocationCode="11"/>
</VehRentalCore>
...
</VehAvailRQCore>
...

Important Fields
Field Required Description
CodeContext Y CARTRAWLER
PickUpLocation_LocationCode Y CarTrawler Location Identifier
ReturnLocation_LocationCode Y CarTrawler Location Identifier



Airport IATA Code

This search type supports one-way rental searching.

<OTA_VehAvailRateRQ
Target="Test"
Version="1.005">
...
<PickUpLocation CodeContext="IATA" LocationCode="LAS"/>
<ReturnLocation CodeContext="IATA" LocationCode="LAS"/>
</VehRentalCore>
...
</VehAvailRQCore>
...

Important Fields
CodeContext Y IATA
PickUpLocation_LocationCode Y IATA 3 character airport code
ReturnLocation_LocationCode Y IATA 3 character airport code



GEO Point

Given any GEO point this message will return availability for the nearest 10 car rental
agent locations within a 25km radius. The number of returned agents and radius
values are subject to change.

<OTA_VehAvailRateRQ
Target="Test"
Version="1.005">
...
<PickUpLocation CodeContext="GEO">51.4660000,-0.4220000</PickUpLocation>
<ReturnLocation CodeContext="GEO">51.4660000,-0.4220000</ReturnLocation>
</VehRentalCore>
...
</VehAvailRQCore>
...

Important Fields
CodeContext Y GEO
PickUpLocation Y Latitude/Longitude value
Format: latitude,longitude
ReturnLocation N Latitude/Longitude value
Format: latitude,longitude

Note: OTA_VehAvailRate message is the only message that supports GEO context.
Other messages should use the CARTRAWLER context. The corresponding Code
for the CARTRAWLER context can be found in the LocationDetails elements of the
OTA_VehAvailRate response.

OTA_VehAvailRateRS:
<VehVendorAvail>
<Vendor Code="206" CodeContext="CARTRAWLER"/>
...
</VehAvails>
<Info>
<LocationDetails Code="0:201793" Name="Sydney - Downtown " AtAirport="0">
...
</LocationDetails>
</Info>
</VehVendorAvail>

Sample, CARTRAWLER context VehRentalCore:
<PickUpLocation CodeContext="CARTRAWLER" LocationCode="0:201793" />
<ReturnLocation CodeContext="CARTRAWLER" LocationCode="0:201793" />
</VehRentalCore>


Car Agent Identifier

Some car agents publish lists of their location identifier values for use by partner
systems. Our system has partial support for this type of searching. We do not publish
car agent location lists. This search type supports one-way rental searching.

<OTA_VehAvailRateRQ
Target="Test"
Version="1.005">
...
<PickUpLocation CodeContext="CAR_AGENT" ExtendedLocationCode="ZT"
LocationCode="LAS">
<ReturnLocation CodeContext="CAR_AGENT" ExtendedLocationCode="ZT"
LocationCode="LAS">
</VehRentalCore>
...
</VehAvailRQCore>
...

Important Fields
CodeContext Y CAR_AGENT
PickUpLocation_ExtendedLocati
onCode
Y Two-digit car agent identifier
PickUpLocation_LocationCode Y Car agent specific location code
ReturnLocation_ExtendedLocati
onCode
Y Two-digit car agent identifier
ReturnLocation_LocationCode Y Car agent specific location code



Multiple Search
(To be phased out, replaced by GEO Point)

Given a comma-separated list of CarTrawler Location Identifiers this message will
return availability first 10 successful locations. This message is limited to return a
max of 2 airport locations. The number of successful locations and airport values are
subject to change. This message does not support search for one-way rentals, any
return location values passed are ignored.

<OTA_VehAvailRateRQ
Target="Test"
Version="1.005">
...
<PickUpLocation CodeContext="CARTRAWLER_MULTI">1,11,13,21</PickUpLocation>
<ReturnLocation CodeContext="CARTRAWLER_MULTI">1,11,13,21</ReturnLocation>
</VehRentalCore>
...
</VehAvailRQCore>
...

Important Fields
CodeContext Y CARTRAWLER_MULTI
PickUpLocation Y Comma-separated list of
CarTrawler Identifiers
ReturnLocation N Comma-separated list of
CarTrawler Identifiers

Note: This location search option must be requested from your CarTrawler Account
Manager. As this message is deprecated permission will only be issued where all
other options have been exhausted.



Mixing Location CodeContext Types

The previous examples detailed how to perform searches with the same search
CodeContext. CarTrawler supports mixed CodeContext requests when searching for
car rental.

For example, to perform a search for pickup at Dublin Airport to return in Dublin City
(51.4660000,-0.4220000) you can set the pickup location using the IATA CodeContext
and the return location to be a particular GEO point.

<OTA_VehAvailRateRQ
xsi:schemaLocation=http://www.opentravel.org/OTA/2003/05 OTA_VehAvailRateRQ.xsd
Target="Test"
Version="1.005">
...
<PickUpLocation CodeContext="IATA" LocationCode="DUB"/>
</VehRentalCore>
...
</VehAvailRQCore>
...

Note: Mixed CodeContexts are only supported by the OTA_VehAvailRateRQ
message. All other messages do not support mixed CodeContexts.

It is possible to mix any supported CodeContext:
IATA
CARTRAWLER
GEO
CAR_AGENT



Advanced One-way Rental Searching

A one-way rental is where the pickup and return locations for the vehicle are
different.

CarTrawler supports one-way rental bookings. Support for one-ways is
straightforward when dealing with 1-to-1 locations, such as Dublin Airport to Cork
Airport.

Example:
<OTA_VehAvailRateRQ
Target="Test"
Version="1.005">
...
<PickUpLocation CodeContext="IATA" LocationCode="DUB"/>
<PickUpLocation CodeContext="IATA" LocationCode="ORK"/>
</VehRentalCore>
...
</VehAvailRQCore>
...

When doing Many-to-Many one-way searches, such as, get all cars for pickup in
Dublin City (51.4660000,-0.4220000) for return in Cork City (51.84900000,-8.47400000).
To achieve this search an additional parameter, OneWayIndicator is added to the
request.

Example:
<OTA_VehAvailRateRQ
Target="Test"
Version="1.005">
...
ReturnDateTime="2009-04-09T19:00:00" OneWayIndicator="true">
<PickUpLocation CodeContext="GEO">51.4660000,-0.4220000</PickUpLocation>
</VehRentalCore>
...
</VehAvailRQCore>
...

If this message was issued without the OneWayIndicator set as true then the
request would not be interpreted as a one-way and the response would contain cars
for pickup and return Dublin City.

Note: 1-to-1 one-way searches do not require the OneWayIndicator to be set.





OTA_VehResRQ
This message is used to book a car based on a car availability response.

<OTA_VehResRQ
xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_VehResRQ.xsd"
Target="Test"
Version="1.005">
<POS>
</Source>
<Source>
<RequestorID Type="16" ID="112233" ID_Context="ORDERID" />
</Source>
</POS>
<VehResRQCore Status="All">
</VehRentalCore>
<Customer>
<Primary>
<PersonName>
<NamePrefix>Mr.</NamePrefix>
<GivenName>Joe</GivenName>
<Surname>Bailey</Surname>
</PersonName>
<Telephone PhoneTechType="1" AreaCityCode="405"
PhoneNumber="5555828"/>
<Email EmailType="2">JoeBailey@work.com</Email>
<Address Type="2">
<AddressLine>123 Elm St., Oklahoma City, 73112,
Oklahoma</AddressLine>
<CountryName Code="US" />
</Address>
<CitizenCountryName Code="US" />
</Primary>
</Customer>
<DriverType Age="29"/>
</VehResRQCore>
<VehResRQInfo PassengerQty="3">
<ArrivalDetails TransportationCode="14" Number="123">
<OperatingCompany>EI</OperatingCompany>
</ArrivalDetails>
<RentalPaymentPref>
<PaymentCard CardType="1" CardCode="VI"
CardNumber="4128000548320918" ExpireDate="0707" SeriesCode="123">
<CardHolderName>Joe Bailey Jr</CardHolderName>
</PaymentCard>
</RentalPaymentPref>
<Reference Type="16" ID="222:1712" ID_Context="CARTRAWLER"
DateTime="2009-02-27T14:45:14.156Z" URL="CT-
DyFJ8dMeoRNFrPCii%2FZSXjoHopVS40JWX0KQrrQwGxvnBHPT%2FT5xGw4sAK%2BF%2FMUzpChnLZGLvuY1%0
AFhMhl5T42fyhqTGz5UccbLN%2BNq94cXuTrs9FDHwvBXQer5ujMZm3EVyzb7bWSzoGm5WtaXTtf4ux%0AvvAL
aJg9"/>
<TPA_Extensions>
<CompanyName VAT="98765">Cartrawler Ltd</CompanyName>
</TPA_Extensions>
</VehResRQInfo>
</OTA_VehResRQ>


Important Fields
Field Description
Attribute Version for OTA_VehResRQ
element.
This must be 1.005
element.
Attribute ID for RequestorID element.
(ID_Context of CARTRAWLER)
The unique id code which identifies you
Attribute ID for RequestorID element.
(ID_Context of ORDERID)
This is an optional code which is your
unique identifier for this reservation.
This is required for invoice purposes, but
is optional.
elements.
VehRentalCore
Vehicle
VehRentalCore
Vehicle
ArrivalDetails element &
OperatingCompany element
Contains Airline code and Flight number
when reservation is for an Airport.
This is optional, but should always be
included for airport locations.
Attribute TransportationCode must
always be 14.
Attribute Number is the Flight number.
Element OperatingCompany should
contain 2 letter Airline code.
Attribute Code for element
CitizenCountryName
The country code of the customers
Must be identical to country of
residence used in OTA_VehAvailRQ
message.
Attribute Age for DriverType element You need to supply the drivers age in this
field.
Must be identical to drivers age used
in OTA_VehAvailRQ message.
Reference element (including all
attributes)
This uniquely identifies the car and its
rate. This element is returned exactly as
it was received from the
OTA_VehAvailRateRs message.
CompanyName element. This is the Company Name associated
with this Reservation.
This is required for invoice purposes.
This is optional.
Attribute VAT for CompanyName
element
This can be used for the VAT number.
This is required for invoice purposes.


This is optional.

NOTE: The drivers Age and the Country of Residence
must be identical to the values passed in the
availability message (OTA_VehAvailRQ).
If they are different, then the OTA_VehResRQ
message will fail.

Life Span for a quote
The Reference element is only valid for a period time after it is created.
Once the Reference element has expired it will not be possible to use it to book a
car.
If you attempt to book a car using a Reference which has expired, you will see the
error message Booking reference not found.
When you see this, you will need to do a fresh availability.

Credit Card required for booking car
The RentalPaymentPref which contain Credit card information should only be
supplied if the car being booked requires a Credit Card..
Each car returned in the availability response has a flag which indicates Credit card
is required to make the booking.

<TPA_Extensions>

<CC_Info Required="true"/>

</TPA_Extensions>


PaymentCard CardCode attribute
Field Description
VI
Visa
MC Mastercard

PaymentCard CardType attribute
Field Description
1 Credit
2 Debit
3 Central bill
We currently support PaymentCard CardType 1, Credit.
Credit Card ExpireDate
The format of the ExpireDate attribute should be "MMYY".
e.g. an expiry date of Jan 2015 would look like "0115".
Flight Information at Airports
If the location is an Airport location, it is advisable to provide Flight Information such
as the airline code and the flight number.
This can be provided using the ArrivalDetails element.

e.g. Customer renting car at airport arriving on flight EI 123.
</ArrivalDetails>

Attribute TransportationCode must always be 14.
Attribute Number is the Flight number.
Element OperatingCompany should contain a 2 letter Airline code.

If the customer is renting a car at an Airport, but is not arriving by a flight, you should
still provide an empty ArrivalDetails element.

e.g. Customer renting car at airport not arriving by flight.
<OperatingCompany>Z9</OperatingCompany>
</ArrivalDetails>

Test Credit Cards on OTATest
These test credit cards can be used on the Cartrawler Test system to make
reservations;
Type Number
Visa 4263971921001307
MasterCard 5425232820001308
You will also need to provide a 3 digit SeriesCode and a valid expiry date.


OTA_VehCancelRQ

This message will cancel a Reservation.
The cancel can fail, depending on the state of the reservation.
If the cancel is successful, it also may issue a refund to the customer.
I
f Cartrawler has not taken the payment, then it will not issue a refund.
The refund it issues can be a partial or a full refund.
In the event of it being a partial refund (the default), it will refund (amount of money
taken from the customer) (your cancellation fee).
Your cancellation fee is a configurable amount that is associated with your POS ID.
<OTA_VehCancelRQ
xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_VehCancelRQ.xsd"
Target="Test"
Version="1.007">
<POS>
<Source>
</Source>
</POS>
<VehCancelRQCore CancelType="Book">
<UniqueID Type="15" ID="IE2527509" />
<PersonName>
</PersonName>
</VehCancelRQCore>
<VehCancelRQInfo>
<RentalInfo PickUpDateTime="2009-05-13T10:00:00" ReturnDateTime="2009-
05-22T13:00:00">
</RentalInfo>

<TPA_Extensions>
<Refund type="FULL"/>
</TPA_Extensions>

</VehCancelRQInfo>
</OTA_VehCancelRQ>


Important Fields
OTA_VehCancelRQ element.
This must be 1.007
Attribute ID for UniqueID element. This is the reservation ID returned to you
in the OTA_VehResRS message.
PersonName element This contains the personal detail
information about the customer who
made the initial Reservation.
This must match the PersonName
from the original reservation or the
Cancel will fail.
RentalInfo element This contains the pickup date/time and
return date/time of your original
reservation. It also contains the pickup
and dropoff location of your original
reservation.
This must match the details of
VehRentalCore from the original
reservation or the Cancel will fail.
Refund element in TPA_Extensions
element.
This is an optional parameter.
If it is included in the message with an
attribute of type = FULL, then a full
refund will be given to the passenger.
Otherwise only a partial refund will be
given.
The value of the partial refund will be the
amount the customer has been charged,
minus your cancel charge.



Example responses

<OTA_VehCancelRS xmlns="http://www.opentravel.org/OTA/2003/05"
Target="Test" TimeStamp=2009-10-07T16:15:15.664Z">
<Success />
<VehCancelRSCore CancelStatus="Cancelled">
<VehCancelRSInfo>
<VehReservation>
<Customer>
<Primary>
<PersonName>
<Surname>Baily</Surname>
</PersonName>
</Primary>
</Customer>
<VehSegmentCore>
<ConfId Type="16" ID="IE2527509" ID_Context="CARTRAWLER" />
<VehRentalCore PickUpDateTime="2009-12-10T10:00:00" ReturnDateTime="2009-12-
12T10:00:00">
<PickUpLocation CodeContext="CARTRAWLER" LocationCode="13" Name="Dublin
Airport" />
<ReturnLocation CodeContext="CARTRAWLER" LocationCode="13" Name="Dublin
Airport" />
</VehRentalCore>
</VehSegmentCore>
<VehReservation>
</VehCancelRSInfo>
</VehCancelRSCore>
</OTA_VehCancelRS>


OTA_VehRetResRQ
<OTA_VehRetResRQ
xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_VehRetResRQ.xsd"
Target="Test"
Version="1.002">
<POS>
<Source>
</Source>
</POS>
<VehRetResRQCore>
<UniqueID Type="15" ID="121212121212" />
</VehRetResRQCore>
</OTA_VehRetResRQ>
Important Fields
Field Description
OTA_VehRetResRQ element.
This must be 1.002
Attribute ID for UniqueID element This is the reservation ID returned to you
in the OTA_VehResRS message.
Optional attribute ID_Context for
UniqueID element. To be used only if
you are looking up the reservation based
on the OrderId recorded at booking time.
ID_Context=ORDERID

Example Response
<OTA_VehRetResRS xmlns="http://www.opentravel.org/OTA/2003/05"
Target="Test" PrimaryLangID="EN" TimeStamp="2009-02-07T16:33:08.441Z">
<Success />
<VehRetResRSCore>
<VehReservation Status="Confirmed">
<Customer>
<Primary>
<PersonName>
<GivenName>John</GivenName>
<Surname>Smith</Surname>
</PersonName>
</Primary>
</Customer>
<VehSegmentCore>
<ConfId Type="16" ID="258762794" ID_Context="CARTRAWLER" />
<ConfId Type="16" ID="IE1234566" ID_Context="RESID" />
<Vendor>VendorName</Vendor>
30T10:00:00">
<PickUpLocation CodeContext="CARTRAWLER" LocationCode="11" Name="Dublin Airport" />
<ReturnLocation CodeContext="CARTRAWLER" LocationCode="11" Name="Dublin Airport" />
</VehRentalCore>
<TPA_Extensions>
<Status>Confirmed</Status>
</TPA_Extensions>
</VehSegmentCore>


<VehSegmentInfo>
<LocationDetails AtAirport="1" Code="11" Name="Dublin Airport" CodeContext="Pickup
Location">
<Address>
<AddressLine>ARRIVALS HALL, DUBLIN</AddressLine>
<CountryName Code="IE" />
</Address>
<Telephone PhoneNumber="+353 1 812 0410" />
</LocationDetails>
<LocationDetails AtAirport="1" Code="11" Name="Dublin Airport" CodeContext="Return
Location">
<Address>
<AddressLine>ARRIVALS HALL, DUBLIN</AddressLine>
</Address>
</LocationDetails>
</VehSegmentInfo>
</VehReservation>
</VehRetResRSCore>
</OTA_VehRetResRS>

Important Fields
Field Description
Attribute ID for ConfId element
ID_Context=CARTRAWLER
Contains the car rental vendor
confirmation number (for a confirmed
reservation)
Attribute ID for ConfId element
ID_Context=RESID
Contains the CarTrawler reservation id
(for a confirmed reservation)
VehRentalCore element. Contains the pickup date/time/location id
and return date/time/location id.
Status attribute of VehReservation
element &
TPA_Extensions/Status element.
Contains status of Reservation. This
could be one of the following;
Confirmed
Unconfirmed
Cancelled
LocationsDetails with attribute
CodeContext of Pickup Location
Location address of the pickup location.
LocationsDetails with attribute
CodeContext of Return Location
Location address of the return location.



No Excess Insurance Quote

This message is used to obtain a quote for the No Excess Insurance product.
An Insurance Quote needs to be requested after every availability request, as the
quotes availability can change depending on the nationality of the driver, cost of the
Rental & duration of the Rental.
OTA_InsuranceQuoteRQ
<OTA_InsuranceQuoteRQ
OTA_InsuranceQuoteRQ.xsd"
Target="Test"
Version="1.002"
PrimaryLangID="en">
<POS>
<Source ISOCurrency="GBP">
</Source>
</POS>
<PlanForQuoteRQ PlanID="ACME" Type="Protection">
<CoveredTravelers>
<CoveredTraveler>
<CoveredPerson Relation="Traveler 1">
<GivenName>John</GivenName>
<Surname>Smith</Surname>
</CoveredPerson>
<CitizenCountryName Code="DK" />
</CoveredTraveler>
</CoveredTravelers>
<InsCoverageDetail Type="SingleTrip">
<TotalTripCost CurrencyCode="EUR" Amount="158.54"/>
<CoveredTrips>
<CoveredTrip Start="2009-09-26T10:00:00" End="2009-09-29T10:00:00">
<Destinations>
<Destination>
<CountryName>NO</CountryName>
</Destination>
</Destinations>
</CoveredTrip>
</CoveredTrips>
</InsCoverageDetail>
</PlanForQuoteRQ>
</OTA_InsuranceQuoteRQ>

NOTE:
You should only change the fields highlighted in bold red.
All other fields should remain unchanged.



Important Fields
element.
Elements GivenName and Surname Contains the name of the customer which
is looking for the Insurance Quote.
Attribute Code of CitizenCountryName
element.
Contains the country code for the
customers country of Residence.
The Insurance offers are based on the
Country of Residence, and the
destination country, so this information is
very important.
Attributes Amount and CurrencyCode
for TotalTripCost element.
Contains the cost of the trip, for which
Insurance is being looked for.
Attributes Start and End for
CoveredTrip element.
Contains the arrival date/time and the
departure date/time for the trip.
Element CountryName Contains the destination country code
where the car rental will take place. The
Insurance offers are based on the
Country of Residence, and the
destination country, so this information is
very important.



OTA_InsuranceQuoteRS
<OTA_InsuranceQuoteRS xmlns="http://www.opentravel.org/OTA/2003/05"
EchoToken="18723222" Target="Test" PrimaryLangID="EN" TimeStamp="2009-06-
25T14:57:57.290+01:00">
<PlanForQuoteRS PlanID="CTWIEST01IE" Name="Car Hire Excess Cover" Type="Protection">
<QuoteDetail>
<ProviderCompany CompanyShortName="MONDIAL" />
<QuoteDetailURL>http://193.58.9.9/CTW/IE/EN/CTW_IE_en_TCs.pdf</QuoteDetailURL>
</QuoteDetail>
<TotalTripCost Amount="114.07" Currency="EUR" />
<PlanCost Amount="18.97" CurrencyCode="GBP">
<BasePremium Amount="22.00" CurrencyCode="EUR" />
</PlanCost>
</PlanForQuoteRS>
<Success />
<TPA_Extensions>
<Data/>
</TPA_Extensions>
</OTA_InsuranceQuoteRS>

Important Fields
Attribute PlanID for PlanForQuoteRS
element.
This is code for the Insurance product
being offered.
This is required in order to book the
Insurance product.
Attribute Name for PlanForQuoteRS
element.
The title of the Insurance product being
offered.
Elements QuoteDetailURL. Insurance Product URL containing the
terms and conditions.
of BasePremium element.
Price of the Insurance product in the
currency which the customer will be
charged in.
of PlanCost element.
Price of the Insurance product in the
requested currency.
Success element. This indicates that the Insurance Quote
message was successful.
Data element. Used to return some interface rendering
code. See Insurance Display section of
documentation.



Insurance Display

The insurance display requirements differ depending on the market where the
insurance is offered. These requirements and business logic make maintaining
insurance offerings difficult and time consuming.

Sample UK Resident Insurance Display

Sample US Resident Insurance Display

To simplify the integration of the various insurance offers we have added some
elements that can be used to dynamically build an insurance display. Using these
display rules will ensure that your site confirms to the insurance offer requirements
and remains up to date with best practice for insurance offerings. All of the
information required for each display is returned via the OTA_InsuranceQuoteRQ
XML call.

It is important to note that any code using these display rules should be built to
handle the Elements in any sequence. It is also important that the Elements are


displayed in order according to their OrderID values. Elements order and values may
be removed or added over time so any code using these rules should be flexible.

Below is a sample of the Elements that are returned.


<OTA_InsuranceQuoteRS
...>
<PlanForQuoteRS PlanID="CTWDK2013-02" Name="Excess Cover Denmark" Type="Protection">
...
</PlanForQuoteRS>
<Success/>
<TPA_Extensions>
<Data>
<Title OrderID="1"><![CDATA[Excess Cover Insurance]]></Title>
<Image OrderID="2"
UIToken="ct_s3_ea_logo_us"><![CDATA[https://cdn.cartrawler.com/insurance/logos/allianz
_global.png]]></Image>
<Paragraph OrderID="3"><![CDATA[Avoid ALL Excess Charges for just GBP 5.85 a
day! Allianz Excess Insurance gives you complete peace of mind. Most companies charge
an Excess, if you have a claim - typically you pay the first EUR 1,000]]></Paragraph>
<List OrderID="4" Title="Our Policy covers:">
<Item><![CDATA[Excess up to GBP 2564.81]]></Item>
<Item><![CDATA[Windows]]></Item>
<Item><![CDATA[Tyres]]></Item>
<Item><![CDATA[Undercarriage]]></Item>
<Item><![CDATA[Roof]]></Item>
</List>
<Paragraph OrderID="5"><![CDATA[Allianz Global Assistance is authorised and
regulated by De Nederlandsche Bank (DNB)]]></Paragraph>
<Links OrderID="6">
<Link OrderID="1" Code="link1" Text="excess reimbursement terms and
conditions" Url="http://213.41.31.43/CTW/DK/EN/CTW_DK_en_TCs.html"/>
</Links>
<Functional OrderID="7">
<Option OrderID="1" Type="CHECKBOX" Enabled="false" Title="I wish to purchase
excess reimbursement insurance for GBP 17.56 (GBP 17.56 = DKK 153.00). I have read and
understand the ${link1}"/>
</Functional>
</Data>
</TPA_Extensions>

Typical Rendering of Display Data




Element Guide

Every UI Element will have an OrderID, this represents the order that the elements
must be given when rendering to the screen.

Display Only Elements
Title
Image
Paragraph
List

Example:
<Title OrderID="1"><![CDATA[Excess Cover Insurance]]></Title>

Complex Elements

Links
So that hyperlinks can be formatted correctly they have been extracted from the
content of other elements. All UI element text values should be searched & replaced
based on the link code values. There can be multiple Link elements per response.

Example:

<Paragraph OrderID="5"><![CDATA[Test of code ${link1}]]></Paragraph>

<Links OrderID="6">
<Link OrderID="1" Code="link1" Text="click here"
Url="http://some.url.com"/>
</Links>

From the example above: Test of code ${link1} would be rendered as:

Test of code <a href=http://some.url.com>click here</a>

Functional - Option
Insurance is an additional product that the customer must choose to purchase. In
some markets this can be an opt-in or partial opt-in product. Some markets require
this selection to be a Radiobutton while others require a CheckBox.

Example:

<Functional OrderID="7">
<Option OrderID="1" Type="CHECKBOX" Enabled="false" Title="I wish to purchase
excess reimbursement insurance for GBP 17.56 (GBP 17.56 = DKK 153.00). I have read
and understand the ${link1}"/>
</Functional>



The Option element can have a Type of RADIO or CHECKBOX. Radioboxes should
be considered a toggle option. If multiple checkboxes are returned then all should be
displayed. The Enabled attribute indicates the option default value. The user should
not be allowed to book insurance unless they have selected the correct option. For
radiobuttons this is indicated by having a selected true option. For checkboxes this is
indicated when all checkboxes are ticked.

Select
Some markets, currently AU, NZ and US require some additional information to
provide an accurate insurance offer. In these cases the information is collected using
a Select control. This allows the implementation and UI to be flexible. The
SelectContol data should be rendered using a HTML Select control. Onchange of the
HTML Select control by the customer a new OTA_InsuranceQuoteRQ should be sent
to ensure an accurate offering.

Example:
<SelectControl OrderID="5" Title="Confirm Age" Type="Age">
<Item Key="23"><![CDATA[21 - 24]]></Item>
<Item Key="30" DefaultValue="true"><![CDATA[25 - 75]]></Item>
</SelectControl>

Example:
<SelectControl OrderID="6" Title="Select State:" Type="State">
<Item Key="" DefaultValue="true"><![CDATA[Please select]]></Item>
<Item Key="AK"><![CDATA[Alaska]]></Item>
<Item Key="CA"><![CDATA[California]]></Item>

</SelectControl>

Booking No Excess Insurance

No Excess Insurance is booked as part of the Car Reservation message.

For the purpose of this document, we will only document the extra elements in the
OTA_VehResRQ message required for booking Insurance


OTA_VehResRQ
This message is used to book a car based on a car availability response.

<OTA_VehResRQ
Target="Test"
Version="1.005">
<POS>
</Source>
<Source>
<RequestorID Type="16" ID="112233" ID_Context="ORDERID" />
</Source>
</POS>
</VehRentalCore>
<Customer>
<Primary>
<PersonName>
</PersonName>
<Address Type="2">
<AddressLine>123 Elm St., Oklahoma City, 73112,
Oklahoma</AddressLine>
</Address>
</Primary>
</Customer>
</VehResRQCore>
<VehResRQInfo>
</ArrivalDetails>
<RentalPaymentPref>
</PaymentCard>
DateTime="2009-02-27T14:45:14.156Z" URL="CT-
DyFJ8dMeoRNFrPCii%2FZSXjoHopVS40JWX0KQrrQwGxvnBHPT%2FT5xGw4sAK%2BF%2FMUzpChnLZGLvuY1%0
AFhMhl5T42fyhqTGz5UccbLN%2BNq94cXuTrs9FDHwvBXQer5ujMZm3EVyzb7bWSzoGm5WtaXTtf4ux%0AvvAL
aJg9"/>
<TPA_Extensions>
<Reference Type="16" ID="CTWIEST01IE" ID_Context="INSURANCE"
Amount="22.00" CurrencyCode="EUR"
URL="http://193.58.223.118/CTW/IE/EN/CTW_IE_en_TCs.pdf"/>
</TPA_Extensions>
</VehResRQInfo>
</OTA_VehResRQ>


Important Fields
Field Description
Attribute Type of
TPA_Extensions/Reference element
Must be 16
Attribute ID of
This is the code for the Insurance product
as returned from the
OTA_InsuranceQuoteRS message.
It is found in the attribute PlanID for
PlanForQuoteRS element.
Attribute ID_Context of
Must be INSURANCE
Attribute Amount of
This is the Amount attribute taken from
the BasePremium element returned in
the OTA_InsuranceQuoteRS message.
Attribute CurrencyCode of
This is the CurrencyCode attribute taken
from the BasePremium element
returned in the OTA_InsuranceQuoteRS
message.
Attribute URL of
This is the URL containing the terms &
conditions of the insurance product,
It is found in the QuoteDetailURL
element of the OTA_InsuranceQuoteRS
message..

The Insurance Quote below shows all the fields that are used to generate the
Insurance Reference for the booking message.
<OTA_InsuranceQuoteRS xmlns="http://www.opentravel.org/OTA/2003/05"
EchoToken="18723222" Target="Test" PrimaryLangID="EN" TimeStamp="2009-06-
25T14:57:57.290+01:00">
<PlanForQuoteRS PlanID="CTWIEST01IE" Name="Car Hire Excess Cover" Type="Protection">
<QuoteDetail>
<ProviderCompany CompanyShortName="MONDIAL" />
<QuoteDetailURL>http://193.58.223.118/CTW/IE/EN/CTW_IE_en_TCs.pdf</QuoteDetailURL>
</QuoteDetail>
<TotalTripCost Amount="114.07" Currency="EUR" />
<PlanCost Amount="18.97" CurrencyCode="GBP">
<BasePremium Amount="22.00" CurrencyCode="EUR" />
</PlanCost>
</PlanForQuoteRS>
<Success />




Cancelling No Excess Insurance
There is no message to cancel the No Excess Insurance product.

If a Reservation has No Excess Insurance associated with it (because it was
requested at reservation time),
then it will be cancelled automatically when the Reservation gets cancelled.



Cartrawler Specific Messages
CT_VehCountrySearchRQ
This is a non OTA standard message used by Cartrawler to retrieve all the country
codes where we have locations.
Because it is non OTA standard we can ignore the OTA restriction of the maximum
number of records returned.

<CT_VehCountrySearchRQ xmlns="http://www.cartrawler.com/"
Target="Test"
PrimaryLangID="EN"
Version="1.001">
<POS>
<RequestorID Type="16" ID="999999" ID_Context="CARTRAWLER"/>
</Source>
</POS>

</CT_VehCountrySearchRQ>
Important Fields
Field Description
CT_VehLocSearchRQ element.
This must be 1.001

Example Response
<CD_VehCountrySearchRS xmlns="http://www.cartrawler.com/"
xsi:schemaLocation="http://www.cartrawler.com/" Version="1.000" Target="Test"
PrimaryLangID="FR" TimeStamp="2009-02-08T14:44:52.035Z">
<Success />
<Countries>
<Country CountryId="AL" Continent="Europe">Albania</Country>
<Country CountryId="AD" Continent="Europe">Andorra</Country>

<Country CountryId="YE" Continent="Asia">Yemen</Country>
<Country CountryId="ZW" Continent="Africa">Zimbabwe</Country>
</Countries>
</CD_VehCountrySearchRS>



CT_VehLocSearchRQ (Pickup locations, Verbose)
This is a non OTA standard message used by Cartrawler to retrieve all the locations
in a country.

<CT_VehLocSearchRQ
xmlns="http://www.cartrawler.com/"
Version="1.000"
Target="Test">
<POS>
<Source>
</Source>
</POS>
<Address>
</Address>
</CT_VehLocSearchRQ>
Important Fields
Field Description
This must be 1.000
element.

Example Response
<CT_VehLocSearchRS xmlns="http://www.cartrawler.com/"
TimeStamp="2009-02-02T14:20:35.034Z">
<Success />
<PopularVehMatchedLocs>
<VehMatchedLoc>
<LocationDetail AtAirport="1" Code="11" CodeContext="CARTRAWLER"
Name="Dublin Airport">
<Address>
<AddressLine>Arrivals Hall, Dublin Airport, Dublin</AddressLine>
</Address>
</LocationDetail>
</VehMatchedLoc>

<VehMatchedLoc>


.
</VehMatchedLoc>

</PopularVehMatchedLocs>
<VehMatchedLocs>
<VehMatchedLoc>
Name="Belfast - Downtown">
<Address>
<AddressLine>96 - 102 Great Victoria Street,, Belfast, BT2 7BE,
Belfast,</AddressLine>
<CountryName Code="OR" />
</Address>
</LocationDetail>
</VehMatchedLoc>

<VehMatchedLoc>
.
</VehMatchedLoc>

</VehMatchedLocs>
</CT_VehLocSearchRS>

The element PopularVehMatchedLocs returns a list of the popular locations in the
country.
The element VehMatchedLocs returns the complete list of locations in the country.
It returns locations in a similar xml structure as defined in the OTA_VehLocSearchRS
message.



CT_VehLocSearchRQ (Pickup locations, Compact)
This is similar to the example above, except the response is more compact.

<CT_VehLocSearchRQ
Version="1.000"
Target="Test">
<POS>
<Source>
</Source>
</POS>
<VehLocSearchCriterion CompactResponse="True" ExactMatch="true"
ImportanceType="Mandatory">
<Address>
</Address>
Important Fields
Field Description
This must be 1.000
Attribute CompactResponse for
VehLocSearchCriterion element.
When this attribute is true the response
is compact and smaller.
element.

Example Response
xsi:schemaLocation="http://www.cartrawler.com/"
Version="1.000"
Target="Test"
TimeStamp="2009-02-02T14:38:53.254Z">
<Success />
<Locations>
<![CDATA[
11=Dublin Airport
1316=Cork Airport
1=Dublin - Dublin South City
=
160=Belfast Downtown

29536=Wexford Downtown
]]>
</Locations>



The response is much smaller than the full XML response.

The Locations CDATA section contain name/value pairs, each location separated by
a carriage return.
Each line in the Locations CDATA section contains a location Id, and a location
name. E.g. 160=Belfast Downtown
160 is the location id
Belfast Downtown is the location name.

There are 2 lists of locations returned, first a list of popular locations (sorted by
popularity), then a list of all locations (sorted alphabetically).
A line with a single = separates these 2 lists.
In the example above, the first 3 locations are popular locations
All the locations after the line containing = are the full list of locations in the country.



CT_VehLocSearchRQ (Return locations, Verbose)
This is a non OTA standard message used by Cartrawler to retrieve the valid return
locations for a supplied pickup location.

<CT_VehLocSearchRQ
Version="1.000"
Target="Test">
<POS>
<Source>
</Source>
</POS>
<PickupLocation ID="11" ID_Context="CARTRAWLER"/>
Important Fields
Field Description
This must be 1.000
Attribute ID for PickupLocation
element.
The pickup location ID

Example Response
TimeStamp="2009-02-02T15:12:48.875Z">
<Success />
<VehMatchedLocs>
<VehMatchedLoc>
<LocationDetail Code="1" CodeContext="CARTRAWLER" Name="Dublin - Dublin
South City" />
</VehMatchedLoc>
.
<VehMatchedLoc>
<LocationDetail Code="31892" CodeContext="CARTRAWLER" Name="Dublin - South
Circular Road" />
</VehMatchedLoc>
</VehMatchedLocs>



CT_VehLocSearchRQ (Return locations, Compact)
This is similar to the example above, except the response is more compact.
<CT_VehLocSearchRQ
Version="1.000"
Target="Test">
<POS>
<Source>
</Source>
</POS>
<VehLocSearchCriterion CompactResponse="True" ExactMatch="true"
ImportanceType="Mandatory">
<PickupLocation ID="11" ID_Context="CARTRAWLER"/>
Important Fields
Field Description
This must be 1.000
Attribute CompactResponse for
VehLocSearchCriterion element.
When this attribute is true the response
is compact and smaller.
Attribute ID for PickupLocation
element.
The pickup location ID
Example Response
TimeStamp="2009-02-02T15:19:00.291Z">
<Success />
<Locations>
<![CDATA[
1=Dublin - Dublin South City
11=Dublin Airport
.
29536=Wexford Downtown
31892=Dublin - South Circular Road
]]>
</Locations>

The response is much smaller than the full XML response.
The Locations CDATA section contain name/value pairs, each location separated by
a carriage return.
Each line in the Locations CDATA section contains a location Id, and a location
name. E.g. 11=Dublin Airport
11 is the location id
Dublin Airport is the location name.


CT_RentalConditionsRQ
This is similar to a OTA_VehResRQ message used to book a car.

<CT_RentalConditionsRQ
Target="Test"
Version="1.000">
<POS>
</Source>
</POS>
</VehRentalCore>
<Customer>
<Primary>
<CitizenCountryName Code="IE" />
</Primary>
</Customer>
</VehResRQCore>
<VehResRQInfo>
<Reference Type="16" ID="11:24:B" ID_Context="CARTRAWLER" URL="CT" />
</VehResRQInfo>
</CT_RentalConditionsRQ>

Important Fields
Field Description
This must be 1.000
elements.
VehRentalCore
Vehicle
VehRentalCore
Vehicle
CitizenCountryName
Reference element (including all
attributes)
This uniquely identifies the car and its
rate. This element is returned exactly as
it was received from the
OTA_VehAvailRateRS message.



Example Response
<CT_RentalConditionsRS xmlns="http://www.opentravel.org/OTA/2003/05"
Target="Test" PrimaryLangID="EN" TimeStamp="2009-04-25T15:43:56.093+01:00">
<Success />
<RentalConditions>
<SubSection Title="Drivers Age">
<Paragraph>No Charge Age: 25 to 65 Years</Paragraph>
<Paragraph>Young Drivers Age: Minimum 23 Years Charge 20 EUR
Includes 21% Tax</Paragraph>
<Paragraph>Younger Drivers Age: Minimum 21 Years Charge 10 EUR per
Month Includes 21% Tax</Paragraph>
<Paragraph>Senior Drivers Age: Maximum 75 Years Charge 20 EUR
Includes 21% Tax</Paragraph>
</SubSection>
<SubSection Title="Drivers License">
<Paragraph>Drivers must hold a full license for 2 years with no
endorsements.</Paragraph>
</SubSection>
<SubSection Title="Additional Drivers">
<Paragraph>Maximum additional drivers 5. Charge per additional driver:
10 EUR Excludes Tax; Excess Amount 123 EUR; On Request</Paragraph>
<Paragraph>No additional drivers charge for One Additional
Driver.</Paragraph>
</SubSection>
<SubSection Title="Coverage / Insurance">
<Paragraph>Third party insurance: Included In Rate</Paragraph>
<Paragraph>Collision damage insurance: Included In Rate; Excess
Amount 1,000 EUR</Paragraph>
</SubSection>
<SubSection Title="Breakdown Assistance">
<Paragraph>Included In Rate</Paragraph>
</SubSection>
<SubSection Title="Fuel Policy">
<Paragraph>Pickup Full, Return Full</Paragraph>
</SubSection>
<SubSection Title="Tax Rate">
<Paragraph>21%</Paragraph>
</SubSection>
<SubSection Title="Payment Method">
<Paragraph>American Express, VISA</Paragraph>
</SubSection>
</RentalConditions>
</CT_RentalConditionsRS>



CT_FleetRQ
This message is used to return Vehicle Details about a specific car,
or all the cars in a country.

Single Car CT_FleetRQ

This form of the message is designed to return information about 1 car type in a
country, identified by a SIPP code.
The SIPP code can be obtained from the OTA_VehAvailRS message.

<CT_FleetRQ
Version="1.000"
Target="Test"
PrimaryLangID="EN">
<POS>
</Source>
</POS>
<Country CodeContext="CARTRAWLER" Code="IE" />
<FleetGroup Code="EDMN" CodeContext="CARTRAWLER" />
</CT_FleetRQ>

Important Fields
Field Description
This must be 1.000
Attribute Code for Country element. The country Code in which the car is
situated
Attribute Code for element FleetGroup The SIPP code of the car in which you
are interested.
This Code is returned in the
OTA_VehAvailRS message, as the
Code attribute of the VehMakeModel
element.

Example SIPP code returned in OTA_VehAvailRS message
<VehAvail>
<Vehicle AirConditionInd="true" TransmissionType="Manual"
PassengerQuantity="5" BaggageQuantity="2">
<VehMakeModel Name="Volkswagen Golf Cabrio or similar" Code="ITMR" />



Example Response

<CT_FleetRS xmlns="http://www.cartrawler.com/"
xsi:schemaLocation="http://www.cartrawler.com/" Version="1.000"
Target="Test" PrimaryLangID="EN" TimeStamp="2010-05-
11T16:45:23.022+01:00">
<Fleet>
<FleetGroup Code="EDMN" CodeContext="CARTRAWLER">
<Vehicle AirConditionInd="false" TransmissionType="Manual"
FuelType="Petrol" DriveType="Unspecified" PassengerQuantity="5"
BaggageQuantity="3" Code="EDMN" CodeContext="CARTRAWLER">
<VehType VehicleCategory="1" DoorCount="4-5" />
<VehClass Size="3" />
<VehMakeModel Name="Ford Fiesta 5dr or similar" Code="EDMN" />

<PictureURL>https://www.cartrawler.com/otaimages/ford/fiesta_nologo
.jpg</PictureURL>
<VehIdentity VehicleAssetNumber="21229" />
</Vehicle>
<SimilarVehicle>Renault Clio 5dr or similar</SimilarVehicle>
<SimilarVehicle>Fiat Punto 5dr or similar</SimilarVehicle>
<SimilarVehicle>Toyota Yaris 5dr or similar</SimilarVehicle>
<SimilarVehicle>Opel Corsa 5dr or similar</SimilarVehicle>
<SimilarVehicle>Suzuki Alto 4dr or similar</SimilarVehicle>
<SimilarVehicle>Peugeot 206 5dr or similar</SimilarVehicle>
<SimilarVehicle>Volkswagen Polo 5dr or similar</SimilarVehicle>
<SimilarVehicle>Citroen C3 5dr or similar</SimilarVehicle>
</FleetGroup>
<EngineDetail EngineSize="1.4" FuelConsumption="76.3"
FuelConsumptionUnit="m/g" CO2Emission="154.0" CO2EmissionUnit="g/km"
/>
<Description>With room for 5 passengers and 3 pieces of luggage, this
model is perfect for small families or groups.</Description>
</Fleet>
<Success />
</CT_FleetRS>



Country wide CT_FleetRQ
This form of the message is designed to return information about all cars available in
a country.

<CT_FleetRQ
Version="1.000"
Target="Test"
PrimaryLangID="EN">
<POS>
</Source>
</POS>
<Country CodeContext="CARTRAWLER" Code="IE" />
</CT_FleetRQ>

Important Fields
Field Description
This must be 1.000
Attribute Code for Country element. The country Code in which the car is
situated



CT_SpecialOffersRQ

This message is used to return special offers for a give client Id and campaign code.
The special offer feed is available using a GET request to a CarTrawler URL.

Feed URL Format

http://www.cartrawler.com/feeds/CLIENTID_OFFERCODE_LANG CURRENCY.xml

* url is also available via https

Example A:
Client ID: 99999
Offer Code: EMAILOFFER
Language: EN
Currency: EUR

http://www.cartrawler.com/feeds/99999_EMAILOFFER_ENEUR.xml

Example B:
Client ID: 99999
Offer Code: HOMEPAGE
Language: FR
Currency: USD

http://www.cartrawler.com/feeds/99999_HOMEPAGE_FRUSD.xml

Important
The offer details are issued by a partners CarTrawler account manager. Locations,
language and currency of feeds are all configurable.

Feeds are updated daily and should be cached daily by the partner website
accessing them.


Example Response

<CT_SpecialOffersRS
xsi:schemaLocation="http://www.cartrawler.com/"
Version="1.000"
Target="Test"
PrimaryLangID="EN"
TimeStamp="2009-10-05T12:29:08.048+01:00">

<Campaign Code="EMAIL_NOV">
<Disclaimer>Prices displayed are a rate based on a 7 day rental for a
mini / economy sized vehicle for pick ups in December 2007.
</Disclaimer>

<Specials Currency="EUR">
<Offer CountryID="IE" LocationCode="11" LocationName="Dublin"
Amount="10" AirportCode="DUB">
<![CDATA[?clientId=99999&...&residence=Ireland]]>
</Offer>
<Offer CountryID="PL" LocationCode="3204" LocationName="Warsaw"
Amount="14">
</Offer>
<Offer CountryID="FR" LocationCode="1670" LocationName="Paris"
Amount="18">
</Offer>
<Offer CountryID="US" LocationCode="884" LocationName="New York"
Amount="22" AirportCode="JFK">
</Offer>
</Specials>

</Campaign>
</CT_SpecialOffersRS>

CT_SpecialOffersRS has one Campaign element and one Disclaimer
element. Each campaign has a Specials elements. Specials include a currency
(Currency attribute). The offer-url is a customised URL that will preload the
clients booking engine with the selected offer. The url includes only the deeplink
parameters not the base URL of the CarTrawler microsite.



Appendix A

Sample Booking
Want to book a car for Mr Joe Bailey,
from 1/May/2006 @ 7am to 9/May/2006 @ 7pm.
Pickup and drop-off locations are Faro International Airport in Portugal.
We also have his credit card details.

Use OTA_VehLocSearchRQ to Search for Location
Search for Location Faro International Airport in Portugal (PT).

<OTA_VehLocSearchRQ
Version="1.005"
Target="Test">
<POS>
<Source>
</Source>
</POS>
<Address>
<CountryName Code="PT" />
</Address>

Important Fields
Field Description
This must be 1.005
element.
The country code PT for Portugal.

Location Response
<OTA_VehLocSearchRS xmlns:xsi="http://www.opentravel.org/OTA/2003/05"
EchoToken="" Target="Test" SequenceNmbr="" TransactionStatusCode="" TimeStamp="2009-
02-27T14:22:28.533Z">
<Success/>
<VehMatchedLocs>
<VehMatchedLoc>
Name="Albufeira">
<Address>


<AddressLine>Edificio Oura Estrela Loja CR
Areias de S. Joao/ Estrada de Sta. Eulalia Albuferia, 8200-381 Portugal</AddressLine>
<CountryName Code="PT"/>
</Address>
<Telephone PhoneNumber="+353 1 490 6173"/>
</LocationDetail>
</VehMatchedLoc>
<VehMatchedLoc>
Name="Cascais">
<Address>
<AddressLine>Av. 25 de Abril (Hotel Cidadela)
Cascais 2754-517 Portugal</AddressLine>
</Address>
</LocationDetail>
</VehMatchedLoc>
<VehMatchedLoc>
Name="Faro International Airport">
<Address>
<AddressLine>Aeroporto de Faro,
Portugal</AddressLine>
</Address>
</LocationDetail>
</VehMatchedLoc>
....
....
</VehMatchedLocs>
</OTA_VehLocSearchRS>

From the OTA_VehLocSearchRS you can see the Location Faro International
Airport was returned, and its Code is 71.
We must use this Location code to identify Faro International Airport.



Use OTA_VehAvailRateRQ to Search for a Vehicle
Search for a Vehicle at Faro International Airport in Portugal (PT) for our date & time
ranges.

<OTA_VehAvailRateRQ
Target="Test"
Version="1.005">
<POS>
<Source ISOCurrency="GBP">
</Source>
</POS>
</VehRentalCore>
</VehAvailRQCore>
<VehAvailRQInfo>
<Customer>
<Primary>
<CitizenCountryName Code='IE' />
</Primary>
</Customer>
<TPA_Extensions>
<ConsumerIP>182.456.432.123</ConsumerIP>
</TPA_Extensions>
</VehAvailRQInfo>

Important Fields
Field Description
OTA_VehAvailRateRQ element.
This must be 1.005
element.
Optional currency field. If present, the
response will use this specified currency.
elements.
71, which is the CARTRAWLER location
code for Faro International Airport.
VehRentalCore
Vehicle
VehRentalCore
Vehicle
Attribute Age for DriverType element This is mandatory.
You need to supply the drivers age in this
field.


Attribute Code for CitizenCountryName
element.
This is mandatory.
This is the country code for the drivers
This is required as different rates may be
available depending on it.
Element ConsumerIP in
TPA_Extensions element.
This will be mandatory.
This is the IP address of your consumers
machine.



Vehicle Avail Response
<OTA_VehAvailRateRS xmlns:xsi="http://www.opentravel.org/OTA/2003/05"
Target="Test" TimeStamp=2009-04-05T16:19:07.689+01:00">
<Success />
<VehAvailRSCore>
09T19:00:00">
</VehRentalCore>
<VehVendorAvails>
<VehVendorAvail>
<Vendor Code="71:222" CodeContext="CARTRAWLER" />
<VehAvails>
<VehAvail>
<Vehicle AirConditionInd="true" TransmissionType="Automatic"
<VehMakeModel Name="Mercedes C 220 AUTOMATIC or similar" Code="PCAR"
/>
<VehType VehicleCategory="1" DoorCount="5" />

<PictureURL>http://www.cartrawler.com/master/GetImage.asp?action=cardetail&id=2095</Pi
ctureURL>
</Vehicle>
CurrencyCode="GBP" />
<Fees>
<Fee Amount="3.40" CurrencyCode="GBP" Purpose="6" />
</Fees>
<Reference Type="16" ID="71:222:1712" ID_Context="CARTRAWLER"
DateTime="2007-11-05T16:19:07.689+01:00" URL=CT/>
</VehAvailCore>
</VehAvail>
<VehAvail>
<Vehicle AirConditionInd="true" TransmissionType="Manual"
<VehMakeModel Name="Volkswagen Golf Cabrio or similar" Code="ITMR" />

<PictureURL>http://www.cartrawler.com/master/GetImage.asp?action=cardetail&id=1650</Pi
ctureURL>
</Vehicle>
CurrencyCode="GBP" />
<Fees>
</Fees>
<Reference Type="16" ID="71:222:1717" ID_Context="CARTRAWLER"
DateTime="2007-11-05T16:19:07.689+01:00" URL=CT/>
</VehAvailCore>
</VehAvail>
</VehAvails>
</VehVendorAvail>
</VehVendorAvails>
</VehAvailRSCore>
</OTA_VehAvailRateRS>



The response is made up of one or more VehVendorAvail, one for each Vendor that
returns availability.
Each VehVendorAvail can contain multiple VehAvail, one for each Vehicle.
Important Fields
Field Description
Attribute Code for Vendor element. This code uniquely identifies the Vendor
which supplies the car.
You can supply this code to
VehicleDetail message to obtain the
Terms & Conditions for all the Vehicles
that Vendor supplies at a location.
22. 22 is the OTA Code for Prepay
amount.
This is the estimated deposit fee that will
be taken from the customer if they book
this vehicle.
23
This is the amount the customer will pay
to the Car Vendor when collecting the
vehicle.
Reference field with all attributes. The Reference field uniquely identifies
the car along with the supplied Rate.
Use this value to book the car using the
OTA_VehRes message.



Use OTA_VehResRQ to Make a Reservation
<OTA_VehResRQ
Target="Test"
Version="1.005">
<POS>
</Source>
</POS>
</VehRentalCore>
<Customer>
<Primary>
<PersonName>
</PersonName>
<Address Type="2">
<StreetNmbr>123 Elm St.</StreetNmbr>
<CityName>Oklahoma City</CityName>
<PostalCode>73112</PostalCode>
<StateProv>Oklahoma</StateProv>
</Address>
</Primary>
</Customer>
</VehResRQCore>
<VehResRQInfo>
<RentalPaymentPref>
</PaymentCard>
DateTime="2007-02-27T14:45:14.156Z" URL=CT/>
</VehResRQInfo>
</OTA_VehResRQ>
Important Fields
Field Description
Attribute Version for OTA_VehResRQ
element.
This must be 1.005
element.
Attribute LocationCode for 71, which is the CARTRAWLER location


elements.
code for Faro International Airport.
VehRentalCore
Vehicle
VehRentalCore
Vehicle
CitizenCountryName
This must match the value supplied in the
OTA_VehAvailRateRQ message.
Attribute Age for element DriverType.

This is mandatory and contains the age
of the driver.
This must match the drivers age supplied
in the OTA_VehAvailRateRQ message.
Element Reference (including all
attributes)
The entire Reference element should be
used to uniquely identify the car and the
rate you wish to book. This value is
returned from the VehAvailRateRS
response.

Vehicle Reservation Response

<OTA_VehResRS xmlns:xsi="http://www.opentravel.org/OTA/2003/05"
EchoToken="" Target="Test" SequenceNmbr="" TransactionStatusCode="" TimeStamp=2009-
03-10T14:32:44.800Z">
<Success />
<VehResRSCore>
<VehReservation>
<Customer>
<Primary>
<PersonName>
</PersonName>
</Primary>
</Customer>
<VehSegmentCore>
<ConfID Type="16" ID="CT2525785" />
<Vendor CompanyShortName="BUDGET" Code="1" CodeContext="CARTRAWLER" />
09T19:00:00">
</VehRentalCore>
<Vehicle AirConditionInd="true" TransmissionType="Automatic"
<VehMakeModel Name="Mercedes C 220 AUTOMATIC or similar" Code="PCAR" />
</Vehicle>
<Fees>
<Fee Amount="4.95" CurrencyCode="EUR" Purpose="6" />
</Fees>
CurrencyCode="EUR" />
<TPA_Extensions>
<ConfID Type="14" ID="295361307" />
</TPA_Extensions>


</VehSegmentCore>
<VehSegmentInfo>
<LocationDetail AtAirport="1" Code="71" Name="Faro International Airport">
<Address>
<AddressLine>Aeroporto de Faro, Portugal</AddressLine>
<CountryName Code="PT" />
</Address>
<Telephone PhoneNumber="+ 351 289 895 760" />
</LocationDetail>
<PaymentRules>
<PaymentRule RuleType="8" Amount="117.19" CurrencyCode="EUR" />
</PaymentRules>
<RentalPaymentAmount PaymentTransactionTypeCode="reserve">
<PaymentCard CardType="1" />
<PaymentAmount Amount="117.19" CurrencyCode="EUR" />
</RentalPaymentAmount>
</VehSegmentInfo>
</VehReservation>
</VehResRSCore>
</OTA_VehResRS>
Important Fields
Field Description
Attribute ID for ConfID element,
Type = 16
The unique id that identifies the
Reservation (generated by
cartrawler.com).
Attribute CompanyShortName for
Vendor element
Name of the Vendor who are supplying
the car.
Attribute ID for ConfID element,
Type = 14, in the TPA_Extensions
element.
This is optional.
It is the Vendors confirmation code.
This is only returned for direct connect
suppliers when the reservation is
confirmed immediately.
LocationDetail element This contains location detail information
specific to the Vendor supplying the car
(including address and telephone
number).



Requesting Special Equipment
When booking a car it is possible to book Special Equipment.
This is sometimes referred to as Optional Extras or Additional Equipment
Examples of Special Equipment include;
Baby Seat
Child Seat
Snow Chains

Special Equipment is vendor specific, as in each Car Vendor have there own list of
Special Equipment which they make available.

Special Equipment availability
The list of Special Equipment available is returned in the OTA_VehAvailRS message.

<VehAvail>
<Vehicle AirConditionInd="true" TransmissionType="Manual" FuelType="Petrol"
DriveType="Unspecified" PassengerQuantity="5" BaggageQuantity="4" Code="CDMR"
CodeContext="CARTRAWLER">
<VehType VehicleCategory="1" DoorCount="4-5" />
<VehClass Size="4" />
<VehMakeModel Name="Opel Astra 5dr or similiar" Code="CDMR" />
<PictureURL>https://www.cartrawler.com/otaimages/opel/astra.jpeg</PictureURL>
</Vehicle>
CurrencyCode="EUR" />
<PricedEquips>
<PricedEquip>
<Description>Baby Seat (0 - 12 mths)</Description>
</Equipment>
<Charge Amount="40.00" CurrencyCode="EUR" IncludedInRate="false" />
</PricedEquip>
<PricedEquip>
<Description>Infant Seat (1-3 years)</Description>
</Equipment>
</PricedEquip>
</PricedEquips>
<Fees>
</Fees>
<Reference Type="16" ID="11:32:5077" ID_Context="CARTRAWLER" DateTime="2007-05-
30T11:56:50.306+01:00" URL="CT " />
</VehAvailCore>
</VehAvail>

There can be a PricedEquips element in every VehAvail element.
This may contain a list of the available Special Equipment.
There will be a PricedEquip element for every Special Equipment available for that
car.
The PricedEquip contains a description of the Special Equipment, a unique identifier
for it, and its cost.



<PricedEquip>
<Description>Baby Seat (0 - 12 mths)</Description>
</Equipment>
</PricedEquip>

Important Fields
Field Description
Attribute EquipType for Equipment
element
The unique equipment id that identifies
this Special Equipment item.
You require this id when requesting this
item.
Description element. Free Text description of the Special
Equipment.
Attribute Amount for Charge element The cost of this Special Equipment for
the Rental duration
Attribute CurrencyCode for Charge
element
The currency for the cost
Attribute IncludedInRate for Charge
element
true if this cost is included in rental.
false if this is an additional cost.



Requesting Special Equipment
Special Equipment are requested using the OTA_VehResRQ message using the
SpecialEquipPrefs element.

05T10:00:00">
</VehRentalCore>
<Customer>
<Primary>
<PersonName>
<GivenName>joe</GivenName>
<Surname>bloggs</Surname>
</PersonName>
<Email EmailType="2">joe@bloggs.com</Email>
<Address Type="2">
<AddressLine>My House</AddressLine>
</Address>
</Primary>
</Customer>
<DriverType Age="30" />
<SpecialEquipPrefs>
<SpecialEquipPref EquipType="7" Quantity="1"/>
</SpecialEquipPrefs>
</VehResRQCore>

The SpecialEquipPrefs Element comes after the DriverType element.

<SpecialEquipPrefs>
</SpecialEquipPrefs>
Important Fields
Field Description
Attribute EquipType for
SpecialEquipPrefs
The unique equipment id that identifies
this Special Equipment item.
You require this id when requesting this
item.
Attribute Quantity for
SpecialEquipPrefs
This is quantity you require, normally this
is 1

In the example above, we are requesting Special Equipment 7 and 8.
From the previous availability, you can see that these are a Baby Seat and a Infant
Seat.

Note: Requests for Special Equipment are passed on to the Vendor.

Note: Requesting Special Equipment will not affect the rate of the car. All costs
associated with Special Equipment are paid directly to the supplier when pickup up
the car.



Appendix B

Common Error conditions

Error
Code
Error Message Explanation
3 No service on requested
date
Supplier does not support
15 Invalid date Invalid pickup/return date
83 Leg/journey/itinerary
reference invalid
Validation check failed.
Pickup date/time/location or Return
date/time/location do not match details in
Reservation.
95 Booking already cancelled Self-Explanatory.
97 Booking reference not
found
The booking reference has expired.
You will need to obtain a fresh Booking
reference by doing a fresh availability.
99 Booking not owned by
requester
Reservation was not created by your POS Id.
161 Search Criteria Invalid The search returned to many records and
cannot be returned.
The OTA Specifies that 100 is the maximum
number of records returned from a Search.
You must narrow the search criteria.
189 Payment not authorised Credit card authorisation refused
193 Cancellation process
failed
Basic validation failed.
Verify that CancelType="Book"
Verify that Reservation ID is present in ID
attribute of UniqueID.
194 No matching bookings
found
Could not find Reservation.
214 Dropoff date time not
within operating hours
Self explanatory
219 Need advance notice for
this pickup time
Self explanatory
226 Pickup date has passed Pickup date for Reservation has already
passed.
227 Pickup date time not within
operating hours
Self explanatory
229 Pickup location not
recognized
Invalid pickup location supplied
233 Return location not Invalid return location supplied


recognized
240 Credit card has expired Credit card expiry date has expired
264 Reservation cannot be
cancelled
Reservation is in a state that prevents it from
being cancelled.
e.g. It is not in a confirmed state.
281 Reservation requires
credit card data
Reservation requires a credit card,
and none is present.
292 Country in address is
invalid
Self explanatory
309 Requested rate may have
changed - note rate
The car supplier is not able to process this
car reservation at this time.
This could be an intermittent problem with the
supplier.
We recommend the customer chooses a
different car.
319 Required data missing:
address
Self explanatory
352 Invalid credit card type Credit card type (i.e. Visa / MasterCard ) is
not supported.
365 Error credit card Generic error occurred processing the credit
card
pickup date
Self explanatory
dropoff date
Self explanatory
Unsupported XML
Request
The Version attribute in the root element of
the request is not supported.
10004 Search returned no
records
The search returned no records.
10005 Error with Credit Card
Processor
A problem has occurred with our Credit Card
Processor.
10006 Location Mismatch The locations passed in the Reservation
message do not match the locations used in
the original availability message.
10009 Invalid Credit Card
Verification number
Self Explanatory
10011 The Credit Card Number
does not correspond to the
Credit Card Type
Self Explanatory
10012 Invalid Credit Card Issue
number
Self Explanatory
10014 Commercial terms vary
between availability and
booking request -
significant variation in
consumer residence or
driver age
This means that key information like drivers
age/consumer residence/currency has
changed between the availability and the
reservation message.
If this is detected then it is not possible to
proceed with the reservation.
The drivers age/consumer
residence/currency must be identical


between these two messages.
drivers age
Self Explanatory
10016 Location must be an
Airport Location
Only Airport locations are allowed for this
Client.
10017 Car is not available Car requested to be booked is no longer
available.
Consumer IP address
Self Explanatory
10020 Invalid VehRentalCore Low level error if no VehRentalCore element
is found in a OTA_VehResRQ message.
10021 Unfortunately we are
unable to process your
booking at this time
The car supplier is not able to process this
car reservation at this time.
This could be an intermittent problem with the
supplier.
We recommend the customer chooses a
different car.
10022 Expiry date invalid Self Explanatory
10023 Card number fails Luhn
Check.Please try again
Self Explanatory
10024 NonNumeric in Credit card
number
Self Explanatory
10026 Expiry month invalid Self Explanatory
Invalid POS ID '???' The POS ID supplied is invalid / disabled.
Currency '??? ' is not
supported
A Currency was specified in the POS that is
not supported.
SeriesCode must be 3
chars or more
Credit card Series code must be 3
characters. This is mandatory, and is the
CVN number for the credit card.
Invalid pickup Location
Invalid dropoff Location
Invalid Reference element Invalid reference number used when
attempting to make a Reservation.
Invalid Vendor code '??' Invalid vendor code used when attempting a
Location Detail Search.
Missing mandatory
parameter 'LocationCode'
LocationCode is mandatory for Location
Detail Search.
No
CARTRAWLER_MULTI
locations.
The list of locations passed in for a
CARTRAWLER_MULTI availability did not
contain an airport location.
This means there are no valid locations in
which to return availability.
Internal Error Generic catch all error for low level system
error.



Appendix C

Certification Process

We have a certification process in place before a client can go live on our production
boxes.
You must request to take part in the certification process by contacting us via our
support page at;

https://partners.cartrawler.com/

The typical Certification process will include
1. We will ask you to provide us with 2/3 sample OTA_VehAvailRateRQ XML
messages for us to review.
2. Once we are satisfied with the XML, we will provide you with credentials for
Production Servers.
3. Moving to production will involve changing the URL you connect to, and
updating the Target attribute of all XML message from Test to Production.
4. We will then ask you to create a Prepaid or Partpaid reservation on
Production for us to review (Do not cancel the Reservation). This reservation
will require a valid credit card. All money will be refunded after the review
process.
5. If you support Postpaid reservations, we will ask you to create a Postpaid
reservation also. This reservation will not require a credit card (and so the
XML must not contain a RentalPaymentPref element).
6. We review the Reservations and their XML (you do not need to provide us
with the XML).
7. After the review, we will cancel the reservations (with full refunds)
8. If everything is ok, you are certified for production access.

NOTE : ONLY BOOK 1 CAR FOR EACH TEST.



Booking Prepaid / Partpaid reservation

A typically Prepaid / Partpaid car could be found using the following details.;

Car Type: ECMN
Pickup Date: 3 to 4 months in the future
Rental Duration: 1 day
Pickup Location: Dublin Airport (Cartrawler Location ID 11)
Dropoff Location: Dublin Airport (Cartrawler Location ID 11)
Residency : IE

Booking prepaid/partpaid reservation

A typically Postpaid car could be found using the following details.;

Car Type: ECAR
Pickup Date: 3 to 4 months in the future
Rental Duration: 1 day
Pickup Location: Los Angeles Airport (Cartrawler Location ID 3716)
Dropoff Location: Los Angeles - Airport (Cartrawler Location ID 3716)
Residency : US

Cartrawler OTA XML

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Cartrawler OTA XML

Загружено:

Авторское право:

Доступные форматы

CarTrawler OTA XML Interface

Вам также может понравиться