Dates change
Access validity is updated. A pending change remains visible until confirmed.
Smart locks · TTLock
Superhostem supports two guest-access approaches: an automatic TTLock PIN tied to a reservation, or a permanent property code managed manually. Connect a compatible lock and manage access validity and PIN changes directly in the app.
Each stay has its own PIN. Superhostem creates and manages automatic TTLock PINs based on the reservation. Save a manual code for the property or an individual stay when needed.
Valid only during the stay
Choose an automatic PIN for each stay or a permanent PIN you manage manually. For manual access, a reservation-specific code can override the shared property code.
A unique PIN for each stay. Superhostem creates and manages it directly on the lock.
The system creates a separate code for each assigned lock and reservation.
6 digits · check-in to check-outThe owner chooses a different code for existing access.
4–9 digits · same validity windowThe reservation controls validity. TTLock must confirm changes.
Save one shared code for the property. Override it for an individual reservation when needed.
Used when the persistent manual PIN method is selected. A reservation override takes precedence.
Shared across multiple staysUse a different, manually created code for one stay instead of the default.
For one specific staySaving a code does not program the lock. Set validity separately in TTLock.
An automatic PIN is created before arrival, works only during the stay and updates when dates change. Requests and confirmations have distinct statuses in the app.
Creation starts automatically 48 hours before check-in. The owner can request it earlier.
After TTLock confirms, the code is ready. It works only within its configured time window.
The PIN expires when validity ends. Removing its record is a separate operation.
Access validity is updated. A pending change remains visible until confirmed.
PIN removal is requested. Until confirmed, its status remains removal pending.
The operation waits or reports an error and is retried. An unconfirmed change is not shown as complete.
See access validity and status for each door alongside the stay. Open PIN management from the same place.
See which doors have a confirmed PIN and exactly when it is valid.
Replace an active code with your own. The stay’s validity window remains unchanged.
Open the history of requests and confirmed operations. PIN values are not stored in it.
Actual app panel with demo data. Open the screenshot to zoom in.
Compatibility and the actual feature scope.
A compatible TTLock lock with V4 passcodes, an available gateway and authorized-admin access. Check the specific model and firmware; a normal eKey is not enough.
The app implements timed reservation PINs and custom replacement. This integration does not offer TTLock’s one-time or recurring PIN types.
Confirmed PINs are available in the verified private guide once the configured access requirements are met. Message templates and email automations can include the effective PIN through the access-code variable. Pending or unavailable access is not sent as a ready PIN.
Yes. Room access and shared entrances are configured separately, and each can use its own manual or TTLock method. A reservation receives access for its assigned rooms and applicable entrances. Private, test, unconfirmed and cancelled stays do not receive automatic reservation PINs.
Cancellation requests code removal. Without an available gateway, the operation may wait for connectivity; the app shows a pending state or an error. Keep a backup entry method.
V4 passcode and gateway requirements: official TTLock documentation.
Connect compatible TTLock locks and manage automatic PINs and manual access codes alongside reservations and online check-in.
Try for free