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 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 403`	Access denied for hotel	Possible reasons are, you are trying to: - retrieve, create or update promotions for a property with the wrong hotel ID. - send requests using machine account that do not have access to the specified hotel ID. - retrieve, create or update promotions for a property which is no longer connected to your interface.	Make sure to specify the correct hotel ID or check your machine account credentials. You can then follow the steps: 1. Check if the property is connected to you in the Provider Portal. 2. Check if the connection status is active in the ‘Properties’ tab in the Provider Portal, using the property ID. 3. Check if the property is added to the machine account you use under ‘Machine Accounts’ in the Provider Portal. To know more about how to use the Provider Portal for the above actions, take a look at this self-help guide.
`HTTP 500`	Internal server error	Possible reason may be that Booking.com systems are experiencing temporary outage.	Try calling the endpoint after some time.

Examples

HTTP/1.1 403 Forbidden

<promotions>
  <fault code="1009">
    <string>Access denied for hotel '23543'</string>
  </fault>
</promotions>
<!-- RUID: [...] -->

HTTP/1.1 400 Bad Request

<promotions>
  <fault code="400">
    <string>code= 1824 level= 2 message= Element 'stay_date', attribute 'start': '2024-06-0' is not a valid value of the atomic type 'xs:date'.
    </string>
    <string>code= 1824 level= 2 message= Element 'promotion', attribute 'id': '2wef' is not a valid value of the atomic type 'xs:integer'.
    </string>
  </fault>
</promotions>
<!-- RUID: [...] -->

HTTP/1.1 400 Bad Request

<promotions>
  <fault code="400">
    <string>Invalid Room id= 124324</string>
    <string>Invalid Room id= 34645</string>
  </fault>
</promotions>
<!-- RUID: [...] -->

Upcoming changes to errors in Q3 2025

We are improving the error handling in our Promotions API by introducing updated error messages and error codes.

These updates are planned for release in Q3 2025.

Upcoming Changes to Promotions API errors

A complete list of the new error messages and codes will be provided here once available.

Examples

HTTP/1.1 400 Bad Request

<promotions>
  <faults>
      <error code="TARGET_CHANNEL_INVALID">"Invalid promotion.target_channel (value=test value)</error>
      <error code="BOOK_DATE_WRONG_SCHEMA">Either both or none of book_date.start and book_date.end should be present</error>
  </faults>
</promotions>
<!-- RUID: [...] -->

HTTP/1.1 400 Bad Request

<promotions>
  <faults>
    <error code="TYPE_INVALID">Invalid promotion.type (value=desktop)</error>
  </faults>
</promotions>
<!-- RUID: [...] -->

HTTP/1.1 400 Bad Request

<promotions>
  <faults>
    <error code="PROMOTION_ID_INVALID">Invalid promotion.id (value=123)</error>
  </faults>
</promotions>
<!-- RUID: [...] -->