4.1. POSSIBLE SEARCH OPTIONS
- Yana Brilevskaya
Analytics
4.1.1. SEARCH BY LOCATIONS
GP Travel HUB offers several alternatives of searching for cars by location.
Search by | Context | Description | Search example |
|---|---|---|---|
City - City | Car will be taken in a location in a city specified, and returned to the same location point or another point in another city. Availability search response will return all possible locations in a cities specified. |
| |
GEO context (one supplier) | When the CodeContext is "GEO.<supplierCode>" then the LocationCode must be specified in GEO context, and then the search request goes only to the supplier specified. So, you can send a request to the particular supplier, even if you don’t know supplier-specific Location Codes. | <VehRentalCore PickUpDateTime="2023-04-01T07:00:00" ReturnDateTime="2023-04-09T19:00:00">
<PickUpLocation LocationType="City" LocationCode="12175" CodeContext="GEO.supplierCode"/>
<ReturnLocation LocationType="City" LocationCode="10785" CodeContext="GEO.supplierCode"/>
</VehRentalCore> | |
supplier context (one supplier) | Allows to specify location codes of certain supplier and get offers only from this supplier. You can use this case if you know exact location codes from suppliers and would like to get offers only from one supplier. | <VehRentalCore PickUpDateTime="2023-04-01T07:00:00" ReturnDateTime="2023-04-09T19:00:00">
<PickUpLocation LocationType="City" LocationCode="BE.BRUGGE" CodeContext="supplierCode"/>
<ReturnLocation LocationType="City" LocationCode="BE.BRUSSELS" CodeContext="supplierCode"/>
</VehRentalCore> | |
customer context | If it is agreed to support customer context, GP Travel HUB can do search by customer-specific location codes. In this case your application can provide your own location code, GP Travel HUB will resolve it via GEO-tree and send requests to supplier. | <VehRentalCore PickUpDateTime="2023-04-01T07:00:00" ReturnDateTime="2023-04-09T19:00:00">
<PickUpLocation LocationType="City" LocationCode="LON" CodeContext="ABC.supplierCode"/>
<ReturnLocation LocationType="City" LocationCode="PAR" CodeContext="ABC.supplierCode"/>
</VehRentalCore>
| |
4.1.2. SEARCH BY AIRPORT
Search by | Context | Description | Search example |
|---|---|---|---|
Airport - Airport |
| Allows to search cars between airports (CodeContext=“IATA.supplierCode” only). Car will be taken in one airport and returned in the same or another. If client returns car in the same airport then DropOffLocation element can be skipped. | |
Airport - City and vice versa | Car will be taken in Airport and returned in some of locations in a City (or vice versa). Availability search response will return all possible locations in a city specified. |
| |
GEO context (one supplier) | Allows to search cars between airport and city (GEO context). Airport CodeContext must be “IATA.supplierCode” only. When the CodeContext of the City Location Type is "GEO.<supplierCode>" then the LocationCode must be specified in GEO context, and then the search request goes only to the supplier specified. So, you can send a request to the particular supplier, even if you don’t know supplier-specific Location Codes. | ||
supplier context (one supplier) | Allows to search cars between airport and city (supplier context). Airport CodeContext must be “IATA.supplierCode” only. Supplier context for City Location Type allows to specify location codes of certain supplier and get offers only from this supplier. You can use this case if you know exact location codes from suppliers and would like to get offers only from one supplier. | ||
customer context | Allows to search cars between airport and city (customer context). Airport CodeContext must be “IATA.supplierCode” only. Customer context for City Location Type allows to do search by customer-specific location codes. In this case your application can provide your own location code, GP Travel HUB will resolve it via GEO-tree and send requests to supplier. |
| |
Airport - Point and vice versa |
| Allows to search cars between airport and pickup/return points. Airport CodeContext must be “IATA.supplierCode” only. Location Code of a Point is supplier-specific, so in order to perform such kind of search you should know it. | |
4.1.3. SEARCH WITH PICKUP/RETURN POINTS
Allows to search for a particular Pickup/Return Points if you already know it. In response, you will get all available offers for these points. The car will be taken in one location point (exactly specified) and returned in another location point (exactly specified).
4.1.4. SEARCH BY VEHICLE
Allows to search for a particular vehicle. Search by vehicle can not stand separately as a kind of search. It always goes with one of the search types mentioned above in the VehPrefs element.
Example of search by vehicle with pickup/return points: