This topic lists all the possible errors you might encounter while using the Market insights API and how to resolve them.
This section captures a list of common HTTP errors you might encounter and possible solutions to fix them. The column old error code captures the old error code which was converted to the OTA error code.
| HTTP Error Code | Old Error Code | OTA Error Code | Message | Description | Reason and Possible Fix |
|---|---|---|---|---|---|
| HTTP 403 Forbidden | FORBIDDEN | 450 | Unable to process. | Can be due to one of the following reasons: - The property is not eligible to retrieve demand data - The provider is not eligible to retrieve demand data - This account doesn't have access to this property - For area_demand_data, no demand data is available for the property's area The provider is not eligible to retrieve property performance data. To retrieve property performance data, providers must be granted Performance data and insights permission by the connected partners. | Possible reasons are, you are requesting data: - for a property with the wrong property ID. - using a machine account that does not have access to the specified property ID. - for a property which is no longer connected to your interface. Make sure to specify the correct property ID or check your machine account credentials. You can get the list of property IDs that are connected to a specify machine accounts by navigating to the Provider Portal and looking under under the ‘Machine Accounts’ tab. In addition, you can check the connection status of properties in the ‘Properties’ tab in the Provider Portal, using the property ID. To know more about how to use the Provider Portal, take a look at the self-help guide. Or, the API returns the error message if the property does not meet certain criteria. To know more about the supported criteria, see Prerequisites. |
| HTTP 400 Bad Request | 394 | Invalid item. | Can occur when you specify an unknown parameter in the request. Make sure to specify the right parameters. | ||
| HTTP 400 Bad Request | 320 | Invalid value. | Occurs when a query parameter has an invalid value. The API returns the name of the parameter in errors.details.fields and, when the parameter accepts a fixed set of values, the accepted values in errors.details.allowed_values. For example, an invalid date_range returns LAST_365_DAYS, LAST_90_DAYS, LAST_60_DAYS, LAST_30_DAYS, LAST_14_DAYS and LAST_7_DAYS as the allowed values. Use one of the allowed values. | ||
| HTTP 400 Bad Request | 321 | Required field missing. | Use the errors.details and errors.description field to identify the missing required fields and a description to help you troubleshoot the error. To know more about the exact fields with missing values, parse the errors.details.fields. | ||
| HTTP 403 Forbidden | 635 | Data not found. | Occurs when the property ID in the request path is not valid, for example when it contains letters. The API returns the description Not found with HTTP 403. Make sure to use the correct numeric property ID. | ||
| HTTP 401 Unauthorized | - | The bearer token is missing, invalid or expired. The errors entry has an empty message and code, and details is null. | To troubleshoot authentication, see the Authentication page. | ||
| HTTP 500 Internal Server Error | Internal server error | Booking.com systems may be experiencing a temporary outage. | Try calling the endpoint again after some time. |