Troubleshooting Market insights API
This topic lists all the possible errors you might encounter while using the Market insights API and how to resolve them.
Working with errors
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 400 Bad Request | 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 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 trying to send updates: - for a property with the wrong property ID. - using machine account that do 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 | 447 | Unable to update - simultaneous updates. | The API is already handling an update request from a previous call for the same property. Retry the request after some time. | ||
| HTTP 400 Bad Request | 497 | Authorization error. | The request contains invalid authentication credentials. Provide the correct authentication details. | ||
| HTTP 400 Bad Request | 320 | Invalid value. | The API returns errors.details and errors.description that captures which part of the request body contains invalid values and a description to help you troubleshoot the error. To know more about the exact fields with invalid values, parse the errors.details.fields. For some fields, the API also returns 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 404 Not Found | 635 | Not found. | Make sure to use the correct property ID or check whether you have provided valid credentials to access the property details. | ||
| HTTP 401 | Access denied | The credentials provided in the request was not sufficient for a successful authentication check. | To fix a failed authentication request, see the Authentication page. | ||
| HTTP 500 | Internal server error | Internal server error | Possible reason may be that Booking.com systems are experiencing temporary outage. | Try calling the endpoint after some time. |