Smart locks: Nuki

ZenHost integrates with Nuki to manage access codes tied to bookings and show them in the portal from the operational arrival time. Creation and revocation depend on the connection and provider response; check the effective validity and status on the lock.

Nuki-side prerequisites

• A Nuki Web account (different from the Nuki mobile app).
• At least one Nuki lock configured and connected.
• An API token generated from your Nuki Web account (advanced settings → API).

Add a Nuki account to ZenHost

Integrations → Nuki menu. The page lists your existing Nuki accounts; click Connect an account.

The form asks for:

• Account name — internal label (e.g. "Nuki house" or "Nuki concierge"). Used to tell accounts apart if you have several.
• Access token — paste your Nuki Web API token here.

Saving stores the account and token. It does not yet confirm that Nuki accepts the token: check that locks can be retrieved when linking the property.

Manage several Nuki accounts

You can have several Nuki accounts in your ZenHost workspace — useful if you manage listings for different owners who each have their own Nuki account, or if you separate operations by entity.

Each account is listed with:

• Its name.
• Its creation date.
• Its last-update date.
• An action menu: Edit, Delete.

When editing, the Access token field can be left empty to keep the existing token (you'd just change the name). If you enter a new token, it replaces the old one.

Link locks to properties

Connecting a specific Nuki lock to a ZenHost property happens from the Setup wizard → Smart locks step, or from a property's record → Locks section. See also Properties & listings → Per-property integrations.

The typical scenario:

1. Connect the Nuki account to your workspace (this page).
2. On each affected property's record, go to the Locks section and pick the Nuki lock to associate (combo box listing the locks detected on the account).
3. ZenHost then auto-creates guest codes for every new booking and surfaces them on the guest portal from the arrival time.

Permissions

Access to the Nuki menu requires read permission on integrations. Creating / editing / deleting a Nuki account requires write permission on integrations. Deletion specifically requires the delete permission.

No connected lock?

If you don't use Nuki, you can still define manual access codes property by property (from the Locks section of a listing's record). These codes aren't auto-generated, but they show up on the guest portal the same way.

Cancellations, times and other devices

The access window follows the booking's operational times, not the guest's estimated time. After a cancellation or date change, read the warnings and check confirmation that connected codes were updated.

A key box uses a static code: it belongs to the property and does not change for each booking. For TTLock, also distinguish offline codes, which may remain valid after cancellation. See TTLock and access code types.