Announcement: API endpoint update to TLS v1.2

Security is very important to us here at OnePageCRM, so we must continuously update every aspect of our software stack to ensure that our applications, and your data, remain safe and secure.

When you visit any secure HTTPS site, including OnePageCRM, your connection is encrypted. The setup of this encryption happens during an initial handshake between your browser and our servers. This encryption is called TLS (Transport Layer Security) or, formally, SSL (Secure Sockets Layer).

There are many versions of SSL/TLS.

  • SSL 2.0 => Deprecated in 2011.
  • SSL 3.0 => Deprecated in 2015.
  • TLS 1.0 => Deprecated in March 2020.
  • TLS 1.1 => Deprecated in March 2020.
  • TLS 1.2 => Current version widely supported.

If you are using a modern web browser and visit a site that doesn’t support TLS v1.2, then you will see an error message telling you the site isn’t secure. Browsers are very good at keeping you informed as they will warn you when a site is not secure.

At OnePageCRM, we will be removing support for TLS v1.0 and TLS v1.1 on July 1st 2020, as part of our best practice and to ensure we are up to date with the most secure version. This is in line with Google Chromes recommendations.

If you’re using the OnePageCRM API, there are some steps, or in true OnePageCRM style, Actions, which you need to take…

You (or your IT team) will need to make sure that your systems support TLS v1.2. In order to help you with this, we have set up an endpoint that only supports TLS v1.2. If your applications work with this endpoint, then you will be all set for the update on July 1st 2020. This endpoint is

In order to test, you can do the following:

  • Test your systems using this endpoint address: Note: This is a test endpoint only and will be disabled on the 1st July 2020. Please do not use it in your production code. This endpoint address is a Production Endpoint so any changes made here affect your data in OnePageCRM.

  • You can use the sample test code below for reference:

A bash one liner:

curl --tlsv1.2 --tls-max 1.2

Ruby Sample code below:

require "net/http"

uri = URI.parse('')
http =, uri.port)
http.use_ssl = true

    request =
    response = http.request(request)
    puts "Thank you. Everything is working"
rescue Errno::ECONNRESET => e
    puts "TLS v1.2 is not supported. Please upgrade your integration."

If you get a 200 OK response, then you are good to go.

If you get an error, then you will need to upgrade your application/environment to support TLS v1.2.

If you have any questions or require any additional information, please leave a comment below, and we will be happy to help you.

Author image

Kevin Farrell

Climbing the never ending learning curve of web development. Currently interested in API design, best practices and in general getting things talking nicely to each other! When not pretending that I can code, I can be found playing the Chinese board game called 'Go' or failing badly at Yoga.