Octorate integration – same PIN on common + apartment doors and automatic deletion after checkout

Nuki APIs Integrations
1

I found the existing Octorate integration topics, but our issue is different and concerns keypad PIN replication across multiple locks and automatic deletion of expired authorizations.
Hello,

Nuki Support has referred us to the developer community regarding two issues with the Nuki–Octorate integration used in our vacation rental properties.

We manage Smartmonki properties in Toledo, Spain, using Octorate as PMS/channel manager and Nuki Smart Locks + Keypads for guest access.

We need clarification on the correct API behaviour so that we can provide this information to Octorate’s technical/integration team.

1. Same PIN on common entrance + apartment door

At our Smartmonki Núñez de Arce property, guests must first pass through a common door before reaching their apartment.

We need the same guest keypad PIN generated for the reservation to be created on:

  • Arce2A → ARCE PISO DERECHA + Arce2A
  • Arce2B → ARCE PISO DERECHA + Arce2B
  • Arce2C → ARCE PISO IZQUIERDA + Arce2C
  • Arce2D → ARCE PISO IZQUIERDA + Arce2D
  • Arce2E → ARCE PISO IZQUIERDA + Arce2E

Can you please confirm the recommended API method for creating the same keypad PIN on multiple Smart Locks?

2. Automatic removal of expired guest authorizations

We currently manage:

  • Smartmonki Núñez de Arce: 7 locks
  • Smartmonki Sinagoga: 9 locks
  • Smartmonki Casa Hércules: 1 lock
  • Total: 17 locks

Guest PINs expire at the end of their permitted access period, but they remain stored in Nuki and we currently have to remove them manually.

We need Octorate’s integration to delete those guest authorizations automatically after checkout, preferably the following day.

Could you please confirm:

  1. The recommended API method for deleting expired keypad authorizations.
  2. Whether the integration should store the authorization ID when creating the PIN so that it can later delete it.
  3. Whether there is any recommended way to verify that the deletion has successfully reached the Smart Lock.

We are not looking to build a separate integration ourselves at this stage. We need the technical information so that the existing Octorate–Nuki integration can be reviewed by Octorate.

Nuki Support has specifically directed us to the developer community for this case.

Thank you very much.

3

Hi,

Thanks for getting in touch.

Before getting to your questions, just a heads up that Octorate has now moved to an external integration, meaning the integration is no longer developed and maintained by Nuki, but by Octorate themselves. If you have any requests regarding the functionality of the integration, please reach out to Octorate.

You can create authorisations for multiple devices using the smartlock/auth endpoint (Swagger UI). This endpoint allows you to define multiple device IDs, so you would pass the ID of the common door as well as the specific apartment door. The same code will be created for both doors.

The recommended approach to deleting authorisations is to use smartlock/{smartlockId}/auth/{id} (Swagger UI). The integration could store the authorisation ID, or could periodically fetch all authorisations on a device and delete those which have expired; this is up to your personal preference. To verify deletion, I’d recommend subscribing to the DEVICE_AUTHS webhooks (Device Triggered Webhooks | Nuki API).

Kind regards,

Andrew