Creating and Managing Smart Lock Access Codes
Access codes are codes for keypad devices. These are used when you want to provide access to a lock using a PIN code.
Last updated
Was this helpful?
Access codes are codes for keypad devices. These are used when you want to provide access to a lock using a PIN code.
Last updated
Was this helpful?
An access code is a code used for a keypad or pinpad device. Unlike physical keys, which can easily be lost or duplicated, PIN codes can be customized, tracked, and altered on the fly. Using the Seam , you can easily generate access codes on the hundreds of door lock models with which we integrate.
Ongoing access code are ideal for residents or long-term users. Ongoing codes start right away and remain active on a device until they are removed.
Time-bound access codes are suitable for temporary access, like guest visits or service appointments. These codes operate between designated starts_at and ends_at timestamps, granting access only during this period.
Hourly-bound offline access codes are intended for shorter durations, while daily-bound offline codes are intended for longer durations. Device manufacturers set the bounds for these short- and long-term access codes, and some device manufacturers enforce a maximum duration for hourly-bound offline access codes. See the corresponding device guide for more information.
Seam ensures access reliability by initiating the programming of access codes onto the lock ahead of its starts_at time. This approach minimizes the risks of delays or disruptions during the programming process.
2N
Dormakaba Oracode
August
Lockly
Igloohome
SmartThings
Kwikset
Nuki
Salto
Schlage
Tedee
TTLock
Yale
Wyze
For those locks that lack native scheduling functionality, Seam will use its own scheduling infrastructure to program the code 60 minutes before the starts_at time, and remove it at the ends_at time.
Note that the name provided on Seam is used to identify the code on Seam and is not necessarily the name that appears on the lock provider's app or on the device. This is because lock providers may have constraints on names, such as length, uniqueness, or characters that can be used. In addition, some lock providers may break names down into components, such as first_name and last_name.
To provide a consistent experience, Seam identifies an access code on Seam by its name but may modify the name that appears on the lock provider's app or on the device. For example, Seam may add additional characters or truncate the name to meet provider constraints.
To help end users identify codes set by Seam, Seam provides the name exactly as it appears on the lock provider's app or on the device as a separate property called appearance. This is an object with a name property and, optionally, first_name and last_name properties (for providers that break a name down into components).
Currently, the following device manufacturers send the access_code_id in the lock.unlocked event:
August
Kwikset
Salto KS
Schlage
Tedee
TTLock
Yale
Seam attempts to keep an access code on a device in sync with the declared state of the access code on Seam. For example, the start time and end time of the access code are set to match the declared state of the access code on Seam. Any updates to the access code timings on Seam are reflected on the device. In general, if the access code is modified externally to Seam (through the lock provider's app, for example), Seam attempts to re-set the access code on the device to match the declared state of the access code on Seam. This also applies if the access code is removed from the device. Seam attempts to re-set the access code on the device, until the declared ending time of the access code has passed.
When external modifications are detected, Seam sends an access_code.modified_external_to_seam event and adds a code_modified_external_to_seam error on the access code.
This behavior can sometimes be surprising to users, so we recommend that you inform your users that Seam attempts to re-set access codes on the device if they are modified or removed externally. If you want to disable this behavior, you can set the allow_external_modification flag to true when creating an access code. When this flag is set to true, Seam sets code_modified_external_to_seam as a warning on the code instead of an error.
Occasionally, Seam may encounter issues when programming codes onto locks. Such hiccups can arise from device connectivity issues, manual interventions from the lock or its accompanying app, or service disruptions from the lock providers. Given these issues, we strongly advise preprogramming a set of backup codes onto the door lock. Should you detect a failure in access code programming, these backup codes can be promptly shared.
Seam supports programming two types of access codes: and . To differentiate between the two, refer to the type property of the access code. Ongoing codes display as ongoing, whereas time-bound codes are labeled time_bound.
In addition, for certain devices, Seam also supports .
Offline access (PIN) codes are designed for door locks that might not always maintain an internet connection. Currently, Seam supports offline access codes for , , and . For this type of access code, the device manufacturer uses encryption keys (tokens) to create server-based registries of algorithmically-generated offline PIN codes. Because the tokens remain synchronized with the managed devices, the locks do not require an active internet connection—and you do not need to be near the locks—to create an offline access code. Then, owners or managers can share these offline codes with users through a variety of mechanisms, such as messaging applications. That is, lock users do not need to install a smartphone application to receive an offline access code.
Seam supports two types of offline access codes: and . Note that this support varies based on the device manufacturer. Before creating an offline access code, it is imperative to understand any manufacturer- or device-specific constraints, such as the maximum number of access codes, any time slot or activation requirements, and so on. For details, see the corresponding device guide.
For and , you can create time-bound offline access codes with validity durations at either the hour level or the day level. For , you can create generic time-bound offline access codes that do not differentiate between hourly-bound and daily-bound codes.
To , specify the desired starts_at and ends_at date and time. To , you must specify the same time in the starts_at and ends_at properties.
For and , you can create . igloohome one-time-use offline access codes are valid for 24 hours from the starts_at timestamp that you configure. Lockly offline access codes are valid for the time period that you specify using the starts_at and ends_at timestamps. These codes expire after a single use.
For locks that support setting codes with a schedule, Seam will preload access codes onto the device a full 72 hours before the starts_at timestamp of a time-bound code. When the starts_at time arrives, the code automatically activates and will remain active until its ends_at time. We enable this "native scheduling" functionality by default for all providers that support it. See for a list of supported providers. You can choose to override this default behavior and have Seam perform "just-in-time scheduling" by setting prefer_native_scheduling to false when creating a code.
When a user unlocks a door using an access code, Seam issues a . Some device manufacturers include the ID of the access code in . This information is useful for troubleshooting and logging. Further, if you name access codes in a way that identifies the associated users, you can use these lock.unlocked events to identify the users who unlocked the doors.
Seam offers a Backup Access Code service. When activated, this service automatically maintain a pool of pre-programmed access codes on a device. These codes are programmed in addition to the regular access codes on Seam, acting as a safety net in case of any issues with the primary codes. Please read about .
ends_at timestamp that you provide to Seam.
starts_at timestamp, Seam inserts the code into the device's internal memory. When the starts_at time arrives, the device automatically activates the code. It is then automatically deactivated at the ends_at timestamp.
starts_at time arrives, Seam adds the code to the device and activates it. It is then automatically deactivated at the ends_at timestamp.