Readonly
defaultsReadonly
ltsStatic
ltsOptional
body: { Optional
allow_Optional
attempt_Optional
code?: stringCode to be used for access.
Optional
common_Key to identify access codes that should have the same code. Any two access codes with the same common_code_key
are guaranteed to have the same code
. See also Creating and Updating Multiple Linked Access Codes.
ID of the device for which you want to create the new access code.
Optional
ends_Date and time at which the validity of the new access code ends, in ISO 8601 format. Must be a time in the future and after starts_at
.
Optional
is_Indicates whether external modification of the code is allowed. Default: false
.
Optional
is_Indicates whether the access code is an offline access code.
Optional
is_Indicates whether the offline access code is a single-use access code.
Optional
max_Maximum rounding adjustment. To create a daily-bound offline access code for devices that support this feature, set this parameter to 1d
.
Optional
name?: stringName of the new access code. Enables administrators and users to identify the access code easily, especially when there are numerous access codes. Note that the name provided on Seam is used to identify the code on Seam and is not necessarily the name that will appear in 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
. To provide a consistent experience, Seam identifies 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 to meet provider constraints. To help your 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).
Optional
prefer_Indicates whether native scheduling should be used for time-bound codes when supported by the provider. Default: true
.
Optional
preferred_Preferred code length. Only applicable if you do not specify a code
. If the affected device does not support the preferred code length, Seam reverts to using the shortest supported code length.
Optional
starts_Date and time at which the validity of the new access code starts, in ISO 8601 format.
Optional
sync?: booleanOptional
use_Indicates whether to use a backup access code pool provided by Seam. If true
, you can use /access_codes/pull_backup_access_code
.
Optional
use_Optional
body: { Optional
allow_Indicates whether external modification of the code is allowed. Default: false
.
Optional
attempt_Optional
behavior_Desired behavior if any device cannot share a code. If throw
(default), no access codes will be created if any device cannot share a code. If create_random_code
, a random code will be created on devices that cannot share a code.
Optional
code?: stringCode to be used for access.
IDs of the devices for which you want to create the new access codes.
Optional
ends_Date and time at which the validity of the new access code ends, in ISO 8601 format. Must be a time in the future and after starts_at
.
Optional
is_Indicates whether external modification of the code is allowed. Default: false
.
Optional
is_Indicates whether the access code is an offline access code.
Optional
is_Indicates whether the offline access code is a single-use access code.
Optional
max_Maximum rounding adjustment. To create a daily-bound offline access code for devices that support this feature, set this parameter to 1d
.
Optional
name?: stringName of the new access code. Enables administrators and users to identify the access code easily, especially when there are numerous access codes. Note that the name provided on Seam is used to identify the code on Seam and is not necessarily the name that will appear in 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
. To provide a consistent experience, Seam identifies 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 to meet provider constraints. To help your 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).
Optional
prefer_Indicates whether native scheduling should be used for time-bound codes when supported by the provider. Default: true
.
Optional
preferred_Preferred code length. Only applicable if you do not specify a code
. If the affected device does not support the preferred code length, Seam reverts to using the shortest supported code length.
Optional
starts_Date and time at which the validity of the new access code starts, in ISO 8601 format.
Optional
use_Indicates whether to use a backup access code pool provided by Seam. If true
, you can use /access_codes/pull_backup_access_code
.
Optional
use_Optional
params: { ID of the access code that you want to delete.
Optional
device_ID of the device for which you want to delete the access code.
Optional
sync?: booleanOptional
body: { ID of the device for which you want to generate a code.
Optional
params: { Optional
access_ID of the access code that you want to get. You must specify either access_code_id
or both device_id
and code
.
Optional
code?: stringCode of the access code that you want to get. You must specify either access_code_id
or both device_id
and code
.
Optional
device_ID of the device containing the access code that you want to get. You must specify either access_code_id
or both device_id
and code
.
Optional
params: { Optional
access_IDs of the access codes that you want to retrieve. Specify either device_id
or access_code_ids
.
Optional
customer_Optional
device_ID of the device for which you want to list access codes. Specify either device_id
or access_code_ids
.
Optional
limit?: numberNumerical limit on the number of access codes to return.
Optional
page_Identifies the specific page of results to return, obtained from the previous page's next_page_cursor
.
Optional
user_Your user ID for the user by which to filter access codes.
Optional
body: { ID of the access code for which you want to pull a backup access code.
Optional
body: { ID of the device for which you want to report constraints.
Optional
max_Maximum supported code length as an integer between 4 and 20, inclusive. You can specify either min_code_length
/max_code_length
or supported_code_lengths
.
Optional
min_Minimum supported code length as an integer between 4 and 20, inclusive. You can specify either min_code_length
/max_code_length
or supported_code_lengths
.
Optional
supported_Array of supported code lengths as integers between 4 and 20, inclusive. You can specify either supported_code_lengths
or min_code_length
/max_code_length
.
Optional
body: { ID of the access code that you want to update.
Optional
allow_Indicates whether external modification of the code is allowed. Default: false
.
Optional
attempt_Optional
code?: stringCode to be used for access.
Optional
device_ID of the device containing the access code that you want to update.
Optional
ends_Date and time at which the validity of the new access code ends, in ISO 8601 format. Must be a time in the future and after starts_at
.
Optional
is_Indicates whether external modification of the code is allowed. Default: false
.
Optional
is_Indicates whether the access code is managed through Seam. Note that to convert an unmanaged access code into a managed access code, use /access_codes/unmanaged/convert_to_managed
.
Optional
is_Indicates whether the access code is an offline access code.
Optional
is_Indicates whether the offline access code is a single-use access code.
Optional
max_Maximum rounding adjustment. To create a daily-bound offline access code for devices that support this feature, set this parameter to 1d
.
Optional
name?: stringName of the new access code. Enables administrators and users to identify the access code easily, especially when there are numerous access codes. Note that the name provided on Seam is used to identify the code on Seam and is not necessarily the name that will appear in 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
. To provide a consistent experience, Seam identifies 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 to meet provider constraints. To help your 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).
Optional
prefer_Indicates whether native scheduling should be used for time-bound codes when supported by the provider. Default: true
.
Optional
preferred_Preferred code length. Only applicable if you do not specify a code
. If the affected device does not support the preferred code length, Seam reverts to using the shortest supported code length.
Optional
starts_Date and time at which the validity of the new access code starts, in ISO 8601 format.
Optional
sync?: booleanOptional
type?: "time_bound" | "ongoing"Type to which you want to convert the access code. To convert a time-bound access code to an ongoing access code, set type
to ongoing
. See also Changing a time-bound access code to permanent access.
Optional
use_Indicates whether to use a backup access code pool provided by Seam. If true
, you can use /access_codes/pull_backup_access_code
.
Optional
use_Optional
body: { Key that links the group of access codes, assigned on creation by /access_codes/create_multiple
.
Optional
ends_Date and time at which the validity of the new access code ends, in ISO 8601 format. Must be a time in the future and after starts_at
.
Optional
name?: stringName of the new access code. Enables administrators and users to identify the access code easily, especially when there are numerous access codes. Note that the name provided on Seam is used to identify the code on Seam and is not necessarily the name that will appear in 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
. To provide a consistent experience, Seam identifies 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 to meet provider constraints. To help your 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).
Optional
starts_Date and time at which the validity of the new access code starts, in ISO 8601 format.
Static
fromStatic
fromStatic
fromStatic
fromStatic
fromStatic
from
Indicates whether external modification of the code is allowed. Default:
false
.