I did some experiments with the swagger interface and had the same error there.
However when reviewing my earlier commands, I noticed that the I wasn’t using the correct smartlock_id.
So the 403 error with response {“stackTrace”: [], “suppressedExceptions”: []} was just because I didn’t supply the correct smartlock_id.
I try to understand your example a bit more. (I dont have currently http bridge but not sure if I buy it whether my scenario be possible). Considering I generated “key” for the user - how I can share it with him?How the user can use this key to open the lock?
I have Nuki keypad - would it be possible to integrate this generated key with the keypad - so i can just share a pin with the user? And user would use keypad to open the lock?
@jroman In the first step a Nuki Bridge is a device to get remote access to your Smart Lock. If you have a Keypad you can create entry codes for that and just give those to guests.
Additionally you can use the Bridge API (locally) and the Web API (needing a Nuki Web account) to automate tasks. Still authorizations are created on the device itself (locally ore remotely if online and reachable through the Bridge).
Hi @MatthiasK,
Thank you very much for your answer yet it is still a bit unclear. Please note I am exploring automated way of creating authorisations - doing it from application works fine.
I believe it is only possible with bluetooth API or manually from mobile app.
I was going trough bridge api spec - but I cannot figure out which endpoint could be used for creating authorisation. I would appreciate if you can point me to some reference reading.
So here we arrive at this very topic Inside authorisation object I can see there is property “code” is it the value that user needs to enter using keypad?
On creation an e-mail with the invite-key is sent to the users EMAIL.
In our case the user is connected to the smartlock correctly (we can see this in the Web version), but no invitation e-mail is sent on creation. The deactivation e-mail is received correctly afterwards. Can we debug this somehow?
Sorry for my later answer. This is our registered email address, correct. We have not received any specific email with KP codes (You mean the PIN codes for the nuki keyboard - correct? Can you send us a sample how this email should look like?
We send out emails for KP codes and/or invites for the custom integrations but in your case, we do not send out an email if you create just a KP code via the Web API. You would have to send it yourself to the guest. In case you create an authorisation, we send out an invite email, like the below:
Hello!
abc@gmail.com has granted you access to a Nuki Smart Lock.
Open this email on your smartphone and click on the button to accept the invitation: [Accept invitation]
You can redeem the invitation once within 48h.
Thank you for the answer. So my understanding is, if I create a nuki key with a KP code the nuki key is created including KP code but Nuki does not send out a invitation email in this case. Correct? So the nuki key is unknown to anybody (only to you) but the KP code is active and can be used by the guest to open the door.
The Web API expects Nuki Device IDs to be sent as an integer. Device IDs are in HEX therefore they need to be converted to DEC. For the Nuki Opener this needs the type as a prefix to ensure unique IDs for Web API usage
Which version of Smart Lock do you have? Since you cannot share the Smart Lock ID on the forum, I would request you to check once more if you are providing the correct ID, which is on your Smart Lock.