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`	Cannot take this action on the specified opportunity	When trying to send `ENABLE` as an action for a `Redirect` opportunity.	`DISMISS` is the only supported action for a Redirect opportunity.
`HTTP 400`	Key actions is required	When the request is missing an `action` element.	Make sure to specify the `action` element.
`HTTP 400`	The opportunity ID was not found	An opportunity with the specified `opportunity_id` does not exist.	Make sure to use the opportunity ID corresponding to a specific property.
`HTTP 400`	'XXXXX' is not an accepted value for key action (in parameter 'actions') -- should be one of: 'DISMISS', 'DONE', 'ENABLE'	The value of the action parameter specified in the request does not match with one of the accepted values.	Make sure to use a suitable action among the following accepted values: `DISMISS`, `DONE` and `ENABLE`.
`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 403`	This account doesn't have access to this property	Possible reasons are, you are trying to send updates: - for a property with the wrong hotel ID. - using machine account that do not have access to the specified hotel ID. - for a property which is no longer in active connection status with 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.