Price Configuration tool

The Price Configuration tool makes it fast and easy to integrate, index, and test your price feeds. You can quickly update your price feeds all in the same place.

This article explains how to use the Price Configuration tool. 

NOTE: The Price Configuration tool is only available to Pull or Hint partners. To use Price Configuration, you must have an active Hotel List Feed in your Hotel Ads account. Learn how to create, upload, and index your Hotel List Feed.

How to access the Price Configuration tool

To access the Price Configuration toolset in your Hotel Ads Center dashboard, follow the directions below:

  1. Log in to your Hotel Ads Center account.
  2. Navigate to Tools in the main menu. 
  3. Select Configure under Prices in the left navigation panel. The Price Configuration view displays, as shown below:

How to use the Price Configuration tool

You can select your delivery mode (Pull or Pull w/ Hints at the top of the page.) Please contact your TAM if you are considering switching your delivery options. Based on your delivery mode, you will see relevant configuration options. 

How to use the Price Configuration tool - Pull 

The Price Configuration tool is broken into 3 different parts:

Follow the directions below to use the Price Configuration tool.  

1. Enter the Endpoint connection details

Use the "Endpoint connection" tab to set up an API endpoint that Google can query for hotel availability and price data.

NOTE: If your endpoint requires authentication in a keystore outside your URL, email your technical account manager (TAM) to set up the keystore. You can use the Price Configuration tool to test a saved keystore authentication.
 

The required fields are:

  • Hostname
  • Port: 
    • If the URL contains "http://", use Port 80
    • If the URL contains "https://", use Port 443 (default) 
  • Path

If there are problems with your API, an error message with specific details about the issue will display. One example reads: “Hotel price not found.” To troubleshoot, test endpoint configuration with randomized itineraries based on your hotel list feed, with length of stay = 1.

Possible errors include: 

  • Connection error. Please check the hotel prices endpoint info.
  • Hotel price not found.
  • Fetching hotel price timeout. Please check the hotel prices endpoint info.
  • Likely external error from partner. Probably need to notify the partner.
  • UNREACHABLE_CONNECT_REFUSED

2. Enter Price indexing configuration details

Use the "Price indexing configuration" tab to enter specific itinerary guidelines and to test your API endpoint. Some fields are required and others are optional.

NOTE: Price Configuration is for basic API set ups and configurations only. 

The required fields for configuring your prices are outlined in the table below:

Field name Required? Applicable for Pull or Hint Details
Maximum indexing rate (hotel itineraries per second or HIPS) Required Pull The number of queries per second your system can support.
Maximum batch size (Hotels per query) Required Pull and Hint The number of hotels Google should query for in each message.
Maximum parallel requests Required Pull and Hint The maximum number of parallel threads your system can support.

After the fields are filled in, click Start indexing to begin. It may take 15-20 minutes to start your process. 

Some common reasons to use the Stop indexing button include: If you plan to fix errors, conduct tests for higher query numbers, or your servers are down. It may take 15-20 minutes to stop your processes.

3. Run a Price test

Use the "Price test" tab to test specific configuration behaviors. If you have any errors, the price test can help debug API issues and has the ability to test the itinerary prices of specific hotels. The required fields are: 

  • Hostname
  • Port: 
    • If the URL contains "http://", use Port 80
    • If the URL contains "https://", use Port 443 (default) 
  • Path
  • Hotel IDs: comma separated list 
  • Check-in date
  • Length of stay (nights): the allowed range is 1 - 30 days 

After you fill in the details you want to test, click Issue a test query. The results of your query will show up directly below your price test details. 

How to use the Price Configuration tool - Pull w/ Hints 

The Price Configuration tool is broken into 4 different parts:

Follow the directions below to use the Price Configuration tool.  

1. Enter the Endpoint connection details

Use the "Endpoint connection" tab to set up an API endpoint that Google can query for hotel price data.

NOTE: If your endpoint requires authentication in a keystore outside your URL, email your technical account manager (TAM) to set up the keystore. You can use the Price Configuration tool to test a saved keystore authentication.

The required fields are:

  • Hostname
  • Port: 
    • If the URL contains "http://", use Port 80
    • If the URL contains "https://", use Port 443 (default) 
  • Path

If there are problems with your API, an error message with specific details about the issue will display. One example reads: “Hotel price not found.” To troubleshoot, test endpoint configuration with randomized itineraries based on your hotel list feed, with length of stay = 1.

Possible errors include: 

  • Connection error. Please check the hotel prices endpoint info.
  • Hotel price not found.
  • Fetching hotel price timeout. Please check the hotel prices endpoint info.
  • Likely external error from partner. Probably need to notify the partner.
  • UNREACHABLE_CONNECT_REFUSED

2. Enter the Hint endpoint connection details

Use the "Hint endpoint connection" tab to set up an API endpoint that Google can query for hotel availability.

NOTE: If your endpoint requires authentication in a keystore outside your URL, email your technical account manager (TAM) to set up the keystore. You can use the Price Configuration tool to test a saved keystore authentication.

The required fields are:

  • Hostname
  • Port: 
    • If the URL contains "http://", use Port 80
    • If the URL contains "https://", use Port 443 (default) 
  • Path

If there are problems with your API, an error message with specific details about the issue will display. One example reads: “No itinerary found in hint response.” This is because there were no available hints on your server. Try running the test a handful more times until a price has changed on your server. Contact your TAM to debug further. 

Possible errors include: 

  • Connection error. Please check the hotel prices endpoint info.
  • No itinerary found in hint response.
  • Fetching hotel price timeout. Please check the hotel prices endpoint info.
  • Likely external error from partner. Probably need to notify the partner.
  • UNREACHABLE_CONNECT_REFUSED
  • Failed to generate URL from connection settings.
  • Fetch response has truncated data.
  • Failed to uncompress the fetch results/Error decompressing gzip content.

3. Enter Price indexing configuration details

Use the "Price indexing configuration" tab to enter specific itinerary guidelines and to test your API endpoint. Some fields are required and others are optional.
NOTE: Price Configuration is for basic API set ups and configurations only. 


The required fields for configuring your prices are outlined in the table below:

Field name Required? Details
Update Interval Required The number of seconds apart Google should query your server.
Maximum batch size (Hotels per query) Required The number of hotels Google should query for in each message.
Maximum parallel requests Required The maximum number of parallel threads your system can support.

After the fields are filled in, click Start indexing to begin. It may take 15-20 minutes to start your process. 

Some common reasons to use the Stop indexing button include: If you plan to fix errors, conduct tests for higher query numbers, or your servers are down. It may take 15-20 minutes to stop your processes.

4. Run a Price test

Use the "Price test" tab to test specific configuration behaviors. If you have any errors, the price test can help debug API issues and has the ability to test the itinerary prices of specific hotels. The required fields are: 

  • Hostname
  • Port: 
    • If the URL contains "http://", use Port 80
    • If the URL contains "https://", use Port 443 (default) 
  • Path
  • Hotel IDs: comma separated list 
  • Check-in date
  • Length of stay (nights): the allowed range is 1 - 30 days 

After you fill in the details you want to test, click Issue a test query. The results of your query will show up below the directly below your price test details. 

You can also test your queries end-to-end by using the “Test hint endpoint” toggle in the Price Test tab. For a given hint message, we will query your server for the available prices and preview 5 of the returned results. 

Related links

Was this article helpful?
How can we improve it?