Troubleshooting and list of error codes
Working with errors
This section captures a list of common HTTP errors you might encounter and possible solutions to fix them.
| HTTP Error Code | Error Text | Reason | Possible Fix |
|---|---|---|---|
HTTP 400 | Authorization error. Access denied of hotel | When trying to send requests for a property for which you do not have an approved connection to use Content API. | Make sure to specify the correct property ID. In addition, you can check the connection type and connection status of the properties under the Properties tab in the Provider Portal, using the property ID. |
HTTP 400 | Authorization error. Access denied while trying to update hotel | When trying to send requests for a property for which you do not have an approved connection to use Content API. | Make sure to specify the correct property ID. In addition, you can check the connection type and connection status of the properties under the Properties tab in the Provider Portal, using the property ID. |
HTTP 400 | Can not create hotel with same (name, lon/lat, address) | A property with identical name, latitude, longitude, and address already exists in Booking.com systems. | Check if the name, latitude, longitude, and address are correct. If the information is correct, you can direct the property partner to seek assistance from the Booking.com local support team. |
HTTP 400 | Cannot change hotel in status (property status) to open | When the request tries to change a property status to open and bookable. Transitioning to certain property status is not supported. | You can direct the property partner to seek assistance from the Booking.com local support team. |
HTTP 400 | Cannot create a hotel because UFI country (countrycode) is different from property country (countrycode) | When the request tries to create a property with both latitude coordinate and longitude coordinate that are not matching with the address. | Check if the latitude, longitude, and address are correct. |
HTTP 400 | Could not autoassign address reliably with position [latitude,longitude] and city 'CityName' | When the request tries to create a property with any of the following coordinates, not matching the address: - latitude - longitude | Check if the values for the latitude and longitude coordinates are correct. |
HTTP 400 | Latitude: Value is not a latitude (a valid latitude (-90-90)), found 'latitude' | When the request tries to update a property with an invalid latitude coordinate. | Check if the latitude coordinate is correct. |
HTTP 400 | Longitude: Value is not a longitude (a valid longitude (-180-180)), found 'longitude' | When the request tries to update a property with an invalid longitude coordinate. | Check if the longitude coordinate is correct. |
HTTP 400 | License required, but not found | This error can occur when the property requires a license either on the property level or room level, but no license information is specified. | You can use the Licences API to retrieve the property's licence requirements data. If the property has questions related to licenses, you can direct the property partner to seek assistance from the Booking.com local support team. |
HTTP 400 | Missing Position element | Latitude and longitude values are missing. | Check or provide values for the latitude and longitude attributes. |
HTTP 400 | Position: Invalid latitude/longitude | This error can occur when any of the following is invalid: - latitude - longitude - latitude and longitude | Check if the latitude, longitude, and address are correct. If the information is correct, you can direct the property partner to seek assistance from the Booking.com local support team. |
HTTP 400 | Room does not have kitchen or kitchenette | When trying to create or update a property with a property class type Apartment, Aparthotel or Condominium but without specifying kitchen or kitchenette in the room type amenities. | Make sure to specify a kitchen or kitchenette as room amenity for Apartment, Aparthotel or Condominium. If the property does not have a kitchen or kitchenette as room amenity, specify a different Property Class Type. |
HTTP 400 | Cannot change language/ latitude/ longitude/ city/ address/ zipcode in status (property status). Please contact the local support for assistance. | When trying to change the following property attributes for a live property that is not in status XML: Being Built: - language - latitude and /or longitude - city - address - zipcode | You can direct the property partner to seek assistance from the Booking.com local support team. |
HTTP 401 | Authorization Required | 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 | Possible reason may be that Booking.com systems are experiencing temporary outage. | Try calling the endpoint after some time. |
HTTP 500 | System Busy, Try again later | Possible reason may be that Booking.com systems are experiencing temporary outage. | Try calling the endpoint after some time. |
Working with warnings
This section captures a list of common warnings you might encounter and possible solutions to fix them.
| Warning Code | Warning Text | Reason | Possible Fix |
|---|---|---|---|
36 | Could not autoassign address reliably due to lon/lat, city mismatch. Please report to Booking.com | When the request tries to update a property with any of the following coordinates not matching the address: - latitude - longitude | Check if the values for the latitude and longitude coordinates are correct. |