Lots of errors when using web api or https://web.nuki.io

I get confused why access to web api doesn’t work for me, or actually it works sometimes, but often it produces lots of various errors.

Using https://web.nuki.io often fails to proceed when clicking the yellow button:

Trying API over commandline:
curl -X GET https://api.nuki.io/smartlock/<removed> -H "accept: application/json" -H "authorization: Bearer <removed>"
I get sometimes curl: (35) schannel: failed to receive handshake, SSL/TLS connection failed
other time it is http 502 Bad Gateway

I also access the API from a JVM app, and it’s same: sometimes it works, sometimes it produces same failures as curl.

While these errors happen, the Nuki Android app still works and can access my devices over bridge.

Can someone explain reason of all these errors? Does it depend on stability of connection of the Nuki bridge? Or is the Nuki API that much unstable?

1 Like

Oh well, now even Android app writes all is “offline”.
I see at https://status.nuki.io that entire Nuki is down.


(at least Shop works :wink: )

Will this happen often?

Looks like nuki web is currently down

Yes, we have problems every week at least once. If you use their API you will probably have to do a lot of retries.


I created a thread ( "code" in auths is now an array instead of "string" - #2 by genesiscz ) because the issues started yesterday and they are getting worse.

Now we’re getting even 429 Too many requests rejection even though we do not send more than 20 requests per minute

And yes, the 502 Bad Gateway error is not related to end device; it’s actually a server stability issue.

That’s good lesson, just when I publish my new pin generator system. It looks I have to generate pins in bigger advance, and let the code to use retry system.

We are currently experiencing issues with the Web API and Nuki Web, which we are trying to resolve.
The status is reflected on our page: Nuki Status Dashboard – Check the Status of Nuki Services
We will notify you either through customer ticket or the status page as soon as the issue is fixed.
We deeply regret the inconvenience caused and appreciate your patience.