Access Codes
Key codes to be programmed on a door lock
access_code
Properties
access_code
PropertiesThe access_code
object has the following properties:
Property | Type | Description |
---|---|---|
| String (UUID) | Unique identifier for the access code. |
| String (UUID) | Unique identifier for the device associated with the access code. |
| String | Code used for access. Typically, a numeric or alphanumeric string. |
| String | Name of the access code. Enables administrators and users to identify the access code easily, especially when there are numerous access codes. |
| String | Unique identifier for a group of access codes that share the same code. |
| Object | Name as it appears on the lock provider app or on the device. This is an object with a |
| String | Current status of the access code within the operational lifecycle. Values are:
|
| Boolean | Indicates whether the code is set on the device according to a preconfigured schedule. |
| Boolean | Indicates whether Seam manages the access code. |
| Enum | Nature of the access code. Values are:
|
| Boolean | Indicates whether a backup access code is available for use if the primary access code is lost or compromised. |
| Boolean | Indicates whether the access code is a backup access code. |
| String (UUID) | Identifier of the pulled backup access code. Used to associate the pulled backup access code with the original access code. |
| Boolean | Indicates whether the access code is waiting for a code assignment. |
| Boolean | Indicates whether changes to the access code from external sources are permitted. |
| Boolean | Indicates whether the access code can only be used once. If |
| Boolean | Indicates whether the access code is intended for use in offline scenarios. If |
| Datetime (ISO 8601) | Date and time at which the time-bound access code becomes active (only relevant for |
| Datetime (ISO 8601) | Date and time after which the time-bound access code becomes inactive (only relevant for |
| Datetime (ISO 8601) | Date and time at which the access code was created. |
| Collection of errors associated with the access code, structured in a dictionary format. A unique
This structure enables detailed tracking and timely response to critical issues. | |
| Collection of warnings associated with the access code, structured in a dictionary format. A unique
This structure enables detailed tracking and timely response to potential issues that are not critical but that may require attention. |
An Ongoing Access Code will be active until it has been removed from the Device. Be sure to leave both the starts_at
and ends_at
fields empty to specify an ongoing Access Code.
A Time Bound Access Code will be programmed at the **starts_at
**time, and removed at the ends_at
time.
Access Code Names
Note that the name
provided on Seam is used to identify the code on Seam, and is not necessarily the name that will appear 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 down names into components such as first_name
and last_name
.
In order to provide a consistent experience, Seam will identify the 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 in order to meet provider constraints.
In order 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 down a name into components).
External Modification
Seam will attempt to keep the access code on the 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 will be set to match the declared state of the access code on Seam. Any updates to the access code timings on Seam will be reflected on the device. In general, if the access code is modified external to Seam (through the lock provider's app for example), Seam will attempt 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 will attempt 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 will send an access_code.modified_external_to_seam
event and add a code_modified_external_to_seam
error on the access code.
This behavior can sometimes be surprising to end users, so we recommend that you inform your users that Seam will attempt to re-set access codes on the device if they are modified or removed externally. If you would like to disable this behavior, you can set the allow_external_modification
flag to true when an access code. When this flag is set to true, Seam will set code_modified_external_to_seam
as a warning on the code instead of an error.
Access Code Error Types
Errors are returned in a list:
Generic Errors
Seam recommends adding error handling logic to you application for each generic error below. Seam may add more generic errors in the future, so your application should include a fallback case if it encounters an unknown generic error code.
See our troubleshooting tips for access codes for our recommended responses to these error codes.
Error Type | Description |
---|---|
| An error occurred when we tried to set the access code on the device. We will continue to try and set the code on the device in case the error was temporary. |
| An error occurred when we tried to remove the access code from the device. We will continue to try and remove the code from the device in case the error was temporary. |
| We detected that the code was modified or removed externally after Seam successfully set it on the device. We will attempt to set the code on the device again. Please advise the user that Seam will re-set codes they modify or remove manually, and to review other lock integrations that may be modifying the codes. |
| An access code called "Foo bar" with the same pin already exists on the device. |
Specific Errors
When Seam is able to provide more specific information beyond one of the generic errors above, one or more errors from the list of specific errors may appear. This gives your application the option to display additional context or suggest provider specific resolutions.
If the device or connected account associated with an access code has an error, it will be attached to the access code alongside any other access code errors. Treat these errors as Specific Errors. See Device Error Types and Connected Account Error Types.
See our troubleshooting tips for access codes for our recommended responses to these error codes.
Error Type | Description |
---|---|
| August has acknowledged a request to program the code, but the access code has not yet been fully moved to the device. The device likely has a flaky internet connection. We will continue to try and set the code on the device. |
| All access code slots on the device are full. |
| The access code format is not correct |
| August lock is missing a keypad |
| August lock was temporarily offline while setting/removing a code, the code should be set/remove when it comes back online |
| An access code with the same pin already exists on the device. |
| Salto site user is not subscribed. This usually means your Salto site has reached its subscription limit. |
| Failed to set code on device after multiple retries. This may be due to a conflict with an existing code on the device, or other software that may be used to manage the device. Please make sure that other applications like like Rboy or Operto are disabled. |
| There are no free slots available on the device. You will need to delete existing codes before more codes can be added to the device. |
| Unable to confirm that the access code is set on the Kwikset device. This is likely due to a duplicate pin code on the device that was set outside of Seam. Please update this access code's 'code' value through Seam Console or by using our access_codes/update endpoint |
| Unable to confirm deletion of the access code from the Kwikset device. It's possible that this access code was deleted from a source other than Seam. Please check the list of access codes on your Kwikset app from a device that is connected to the lock via Bluetooth or contact us for further assistance |
Access Code Warnings
An access code can have more than one error or warning.
Warnings are returned in a list:
Warning Type | Description |
---|---|
| We expected the device to report that the access code has been removed but it still has not. We will continue to try and remove the code from the device. |
| There was an unusually long delay in programming the code onto the device. For time bound codes, this is sent when the code enters its active time. Note that this is a temporary warning and might be removed if the code is successfully set. |
| When we detect that a code was modified or removed externally after Seam successfully set it on the device, and the |
access_code
Methods
access_code
MethodsLast updated