Disappointed with Nuki Web (beginner)

I am really disappointed with Nuki Web.

I think the developers live in their bubble and don’t understand what you basically want from a door lock with internet connection.

  1. open
  2. close
  3. status if closed or open.

My life time is too waste to learn swagger or whatever.

Why can’t you just generate a key and list examples of URL’s under the device how it opens and closes.

Din the documentation is always from scops the language and always the same example with uploading a configuration file, which a normal user surely wants as the first function. *irony off

I am really disappointed, every question the forum goes in this direction is always referred to the same documentation instead of a simple URL that would solve all the questions.

What is this example?
test.com&client_id=******************&scope=account notification smartloc
k smartlock.readOnly smartlock.action smartlock.auth smartlock.config s

Please just provide 3 URL.




Also a gitHub repo with examples in (e.g php, c++, etc) wouldn’t be too much to ask for this price.

web request version:
url: https://api.nuki.io/smartlock/<LOCK_ID>/action/unlock
Content-Type: application/json
Authorization: Bearer

DeviceID / Smartlock-ID (LOCK_ID) where do you see it?

greetings from Switzerland.


Hello Alf,

Welcome to the Developer forum!

Thank you for your suggestions on Swagger documentation and we will see how we can make it more user-friendly in the future.

I didn’t quite understand your issue - is it in Nuki Web or is it with the Web API documentation?

If you are looking for a device ID in Nuki Web, please login to Nuki Web and ensure your device is see in the “Devices” menu. When you click on a device, you will see “Manage Device” option at the top right and when you click on this button, you will find the ID in the dialog that opens.

If you are looking to call an endpoint through the Web API, refer to the documentation, for example: Swagger UI
Here you can click on the “Model” for more explanation but I paste this below for your reference:


action* integer($int32)
minimum: 0
maximum: 7

The action: type=0/3/4: 1 … unlock, 2 … lock, 3 … unlatch, 4 … lock ‘n’ go, 5 … lock ‘n’ go with unlatch; type=1: 1 … unlock; type=2: 1 activate ring to open, 2 … deactivate ring to open, 3 … open (electric strike actuation), 6 … activate continuous mode, 7 … deactivate continuous mode
option integer($int32)
minimum: 0
maximum: 7

The option mask: 0 … none, 2 … force, 4 … full lock


You can refer to the Model for the endpoints that you are interested in. Please let me know if you have any questions.