Creating temporary access via API question

[Gerardg (Gerard)]

Hi all,

I’m planning to integrate with the Nuki API so that when a booking from a 3rd party booking system is confirmed, I plan to create a temporary 6-digit access code valid for a date/time window via the API and then i’ll email this to the user. This code would grant them access via Nuki for a specified period.

I’ll start working on this integration next week for a friend, but I have one question I haven’t been able to find an answer to:

When a temporary access code is generated for the Nuki, and it is either used or expires, does it need to be revoked or deleted via the API? My main concern is eventually having duplicate codes - if the same code is generated again after the previous one expired, will it be recognised correctly?

Thanks in advance for any clarification.

Gerard

[Juergen (Jürgen Pansy)]

@Gerardg

When a temporary access code is generated for the Nuki, and it is either used or expires, does it need to be revoked or deleted via the API?

Yes. Nuki does not automatically delete Keypad codes. It’s highly recommended to delete any invalid codes from the system (the fewer codes are stored, the more reactive everything is).

@Gerardg

if the same code is generated again after the previous one expired, will it be recognised correctly?

You will get an error if you try to create a code that already exists. But be aware that the Nuki API is mostly async. Make sure to read the documentation linked here. It contains further informations you should be aware of when creating a Keypad code.