To successfully connect your software to the Booking.com Connectivity APIs, your software must use the correct TLS version and cipher suites. You can test if this is the case by sending an API request to our dedicated TLS test host:
The TLS test host works the same as the normal API host (
https://secure-supply-xml.booking.com). If you can call an endpoint on the normal host, you can also call it on the TLS test host. Find details about each endpoint in our API documentation.
NOTE: The TLS test host uses the same database as the normal API host. This means that any API request you send to the TLS test host will modify actual live data, as if you had sent a request to the real API.
Your TLS version and ciphers are correct if your API request gets a response from the TLS test host. Any response will do, regardless of whether the response code is
404, or something else.
If your API request results in a connection error, your TLS version and/or ciphers are not accepted. The format and content of the error message depends on your software stack.
For a list of accepted ciphers, see About TLS & cipher suites.