Hi everyone,

I hope you are having an enjoyable summer.

You may recall we announced in May that support for API requests using HTTPS with TLS 1.0 or 1.1 will end on 15th of September.

Many users of our API have made the switch, only 4% of API requests are currently made using TLS < 1.2. If you haven’t yet made the switch your service may end on 15th of September. (We will try to work with customers if they need a bit longer, but free trial usage will definitely end).

To help those of you still making the switch, we have set up a new testing URL. Instead of querying https://api.opencagedata.com you can test against https://test-new-tls.opencagedata.com which no longer supports TLS 1.0 or 1.1

So for example you can send a request like https://test-new-tls.opencagedata.com/geocode/v1/json?q=51.952659%2C7.632473&key=YOUR-API-KEY&pretty=1

If that request works you are all set and all will keep working after September 15th. If not, you are using TLS 1.0 or 1.1 (or TLS 1.2 with a cipher we don’t support), and need to upgrade as soon as possible.

You can see which ciphers we support by using the excellent SSL Report, provided by Qualys SSL Labs (note the page takes a while to load).


Many of the users we have seen who are still using older TLS version are using the programming language .NET. Here is an article explaining how to make TLS 1.2 the default in older versions of .NET.

After the transition https://test-new-tls.opencagedata.com/ will go away and redirect to https://api.opencagedata.com. Please use it just for testing.

Please get in touch if you are having any difficulties or if there is any way for us to assist you in the transition. Now is the time.

Happy (and secure) geocoding,