Troubleshooting

Help & support

If you need help with developing your integration, check out the Developer Forum for similar topics. If you can’t find the answer to your question, feel free to create a post and a member of the community will be able to share their wisdom with you.

Unfortunately we at Nuki do not provide direct customer assistance for individual integrations.

Service Availability

Always stay up-to-date with our maintenance windows and potential service outages via our status page.

Troubleshooting

I get a 2xx response, but I don’t see my authorisation, keypad code etc.

As our API is asynchronous, a 2xx status code doesn’t necessarily mean your request was successful.

Check out the above link for more detailed information on how our asynhronous API works and what you need to consider in your implementation.

I don’t see the smart lock authorisations that I created via the app

If you have granted authorisation to your smart lock via the smartphone application using bluetooth, it could be that this authorisation is only stored on the device and hasn’t been sent to the server yet. This is an intentional design decision to increase the battery life of your smart lock.

The smart lock will sync data with the server every 24 hours. It may be that this sync was before you last made any changes on your smart lock.

You can force an update of your smart lock via Nuki Web, or via the dedicated sync endpoint.

I receive CORS errors when sending API requests

We’ve implemented a Cross-Origin Resource Sharing (CORS) policy which only allows access from a strict list of trusted domains and subdomains, and do not support the null origin.

You should proxy your request through your own server, so that the server makes the request to https://api.nuki.io on behalf of your web application.