After this date you will no longer be able to make requests to ClubReady end points with the HTTP protocol.
All requests need to be modified before this date to utilize the HTTPS via TLS 1.2. Earlier versions of TLS (1.0, and 1.1) are no longer supported due to security vulnerabilities.
Live Test On June 27th
ClubReady will be testing this change in production, for 2 hours, starting at 1pm Central Time on Wednesday June 27th, 2018. This will allow us to implement the change, and log any requests that come in during that time so that we can identify requests that haven't been properly updated. If you haven't changed your calls by this date, any calls during this time frame will fail.
Does this impact me?
That question is best answered with another question, do you utilize the ClubReady API in any way? Typically this is done via a third party piece of software, an integration, that puts Leads from your website into your ClubReady application, or perhaps a Mobile app that uses the ClubReady for scheduling. If you haven't developed a custom tool to add leads into ClubReady, or a custom website to perform sales within ClubReady's API you likely don't have anything to worry about.
Why is ClubReady making this change?
To further enhance security of our systems, and your data, we are proactively making this change.
What if I'm using a different API?
If you are using http://www.clubready.com/api this change will impact you just the same. We also recommend that you change your API path to be https://www.clubready.com/api/current/ for all future requests.
Read More at weblogs.asp.net:443