Requiring TLS 1.2 on the Cliniko API - May 1, 2018


#1

From May 1, 2018, Cliniko will no longer support TLS 1.0 or TLS 1.1 on the API (api.cliniko.com). API clients and integrations that do not support TLS 1.2 will not work after this date.

This change does not impact regular access to Cliniko (via the web browser), but if you notice anything strange happening with a third party integration, you may want to contact them about it.

Why are we making this change?
Security is very important to us and that’s why we are dropping support for the older, vulnerable TLS versions.

We have already made the change to TLS 1.2 for clients accessing Cliniko not via the API in April 2017.

How do I test my API client?
You can test your API Client by making a request to https://tls-test.cliniko.com/.
If the request is successful, the tls-test endpoint will return a HTTP status code of 200 and also an “OK” in the response body. Otherwise, your client may throw an error regarding the connection failing.


Cliniko This Week - 16th February 2018