/
2.1. POSSIBLE SEARCH OPTIONS

2.1. POSSIBLE SEARCH OPTIONS

2.1.1. SEARCH BY LOCATIONS

GP Travel HUB offers several alternatives of searching hotels by location:

 

Search by

Description

Search example

 

Search by

Description

Search example

1

City code from supplier context (one supplier)

Allows to specify city code of certain supplier and get hotel 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 some supplier.

<Criterion> <HotelRef HotelCityCode="LON" HotelCodeContext="supplierCode"/> </Criterion>

2

City code from customer context

If it is agreed to support customer context, GP Travel HUB can do search by customer-specific city codes. In this case your application can provide your own city code, GP Travel HUB will resolve it via GEO-tree and send requests to supplier.

 

<Criterion> <HotelRef HotelCityCode="LON" HotelCodeContext="ABC.supplierCode"/> </Criterion>
  • In this example "ABC" is a customer identifier. Ask about your specific identifier during integration.

3

GEO Search context

Allows to use City Code from supplier context, and then send search request to all suppliers. HotelCodeContext value like "<supplier>.GEO" is used for this.

<Criterion> <HotelRef HotelCityCode="LON" HotelCodeContext="supplierCode.GEO"/> </Criterion>

4

Pagination search

Allows to receive results in parts. To start a pagination search AllowPartialAvail attribute should be true in Availability request. HUB returns available offers until MoreIndicator is true on Availability response. Pagination search can be interrupted after each Availability request. If part of received offers is enough no need to send other Availability requests despite the fact that the MoreIndicator is true on Availability response. Check diagram below for case when you should receive all available offers:

You can see pagination search example after diagram below.

Diagram 2.1.1.1. Pagination search process.

Pagination search can be interrupted after each Availability request. If part of received offers is enough no need to send other Availability requests despite the fact that the MoreIndicator is true on Availability response.

First Availability request with AllowPartialAvail="true":

First Availability response with MoreDataEchoToken and MoreIndicator="true":

Second Availability request with AllowPartialAvail=true and MoreDataEchoToken from previous Availability response:

Second Availability response with MoreDataEchoToken and MoreIndicator="false":

2.1.2. SEARCH BY HOTEL

Search by

Description

Search example

Search by

Description

Search example

Hotel code from supplier context

If you already did search, you can check just availability of certain hotel. In this case you need to provide supplier city code and hotel code as a search criteria.

Hotel name

Allows to perform search by hotel name. Full hotel name or part of it can be specified.

List of hotels

Allows to perform search by list of hotel codes.

Note: This functionality supported for limited suppliers. Please check with GP Travel HUB development if you are interested in specific supplier.

 

In case of search by list of hotels from one city you need to provide supplier city code and codes of each hotel as a search criteria.

In case of search by list of hotels from different cities you need to provide supplier city codes and codes of each hotel of appropriate city as a search criteria.

2.1.3. SEARCH BY COORDINATES

Search by

Description

Search example

Search by

Description

Search example

Coordinates

Allows to perform search, specifying latitude and longitude of a point as well as radius of search. Refers to OTA Unit of Measure Code.

Note: HUB uses internal logic listed below for search by coordinates only if supplier does not support this kind of search. If it is supported by supplier then HUB just passes coordinates to supplier.

 

 

In case of request with GEO code, search is performed by HUB in following way:

  • all locations are extract from database from GEO tree. Then by mappings we extract supplier's locations and make search.

  • results are filtered to compute distance and the closest location considering Radius/@Distance to reseive only suitable locations.

by Geo context

In case of request with supplier code, search is performed by HUB in following way:

  • all locations are extract from database from Supplier tree. This means search can be made if we have latitude and longitude in supplier's static data only.

  • results are filtered to compute distance and the closest location considering Radius/@Distance to reseive only suitable locations.

by supplier context

Quadrangle

Allows to specify the quadrangular area of search by defining its south-west and east-north coordinates. In response HUB returns all hotels that are located into specified area.

 

2.1.4. SEARCH FOR MULTIPLE ROOMS REQUESTED

GP HUB allows to do an availability search for multiple rooms at one time.

Related content

1.1. GENERAL WORKFLOW
1.1. GENERAL WORKFLOW
More like this
2.2. HOTEL AVAILABILITY REQUEST
2.2. HOTEL AVAILABILITY REQUEST
Read with this
2.1. POSSIBLE SEARCH OPTIONS
2.1. POSSIBLE SEARCH OPTIONS
More like this
2.3. HOTEL AVAILABILITY RESPONSE
2.3. HOTEL AVAILABILITY RESPONSE
Read with this
4.1. POSSIBLE SEARCH OPTIONS
4.1. POSSIBLE SEARCH OPTIONS
More like this
1.3. COMMON REQUEST HANDLING
1.3. COMMON REQUEST HANDLING
Read with this