Hi everyone,

As announced here in the blog in May, and reminded a few weeks ago, and numerous times via our twitter account, from today (15 September 2020) we will no longer support API requests using HTTPS with TLS 1.0 or 1.1.

The switch has been flipped and from now any such request will receive a response with status of 426 and the message Upgrade required (unsupported TLS).

Here’s an example of such a response (made using curl and forcing it to use TLS 1.1)

$ curl --tlsv1.1 --tls-max 1.1 'https://api.opencagedata.com/geocode/v1/json?q=51.952659%2C%207.632473&key=YOUR-API-KEY&language=en&pretty=1'
   "documentation" : "https://opencagedata.com/api",
   "licenses" : [
         "name" : "see attribution guide",
         "url" : "https://opencagedata.com/credits"
   "results" : [],
   "status" : {
      "code" : 426,
      "message" : "Upgrade required (unsupported TLS)"
   "stay_informed" : {
      "blog" : "https://blog.opencagedata.com",
      "twitter" : "https://twitter.com/OpenCage"
   "thanks" : "For using an OpenCage API",
   "timestamp" : {
      "created_http" : "Tue, 15 Sep 2020 11:31:10 GMT",
      "created_unix" : 1600169470
   "total_results" : 0

If this has broken your geocoding the possible solutions are

  1. switch to requesting via http rather than https.

  2. use TLS 1.2 or greater. How you make the upgrade will depend on the programming language you are using. Do a quick searchand I am sure you will find helpful resources explaining how to upgrade.

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

Happy (and secure) geocoding,