Skip to main content
A backup access code pool is a collection of pre-programmed access codes stored on a device, ready for use. These codes are programmed in addition to the regular access codes on Seam, serving as a safety net for any issues with the primary codes. If there’s ever a complication with a primary access code—be it due to intermittent connectivity, manual removal from a device, or provider outages—a backup code can be retrieved. Its end time can then be adjusted to align with the original code, facilitating seamless and uninterrupted access. To bulletproof your implementation of access codes, it’s essential to maintain a pool of backup access codes for each device. Seam provides a robust implementation of this backup pool system, and this article will help you learn how to use our backup access pool system.
Seam supports backup access codes for time-bound access codes only.

​
Before You Begin

To confirm that Seam supports back up code pools for your device, check the device’s properties by inspecting the response from Get Device or List Devices. Ensure that the device’s properties.supports_backup_access_code_pool is true. After you’ve done that, come back here and keep reading. Example Payload: 
{
    "device_id": "00000000-0000-0000-0000-000000000000",
    "properties": {
        "supports_backup_access_code_pool": true,
        ...
    },
    ...
}
Request: 
console.log(
  await seam.devices.get({
    device_id: '6aae9d08-fed6-4ca5-8328-e36849ab48fe',
  }),
)
Response: 
{
  device_id: '6aae9d08-fed6-4ca5-8328-e36849ab48fe',
  .
  .
  .
  properties: {
    .
    .
    .
    supports_backup_access_code_pool: true
  },
  .
  .
  .
}

​
Enabling and Retrieving Backup Codes

​
1. Activate the backup access code pool

To activate the backup pool, set use_backup_access_code_pool to true when creating an access code. After activation, the backup access code pool cannot be turned off for that device. However, if you unmanage the device, any backup access codes are removed. This activation is a one-time process for each device. Once initiated, Seam consistently maintains a backup code pool for the device. All access codes associated with the device utilize the same backup code pool.
In the smart lock app, backup access codes appear as “Backup {CODE_ID} (Seam)”.
Request: 
const deviceId = '6aae9d08-fed6-4ca5-8328-e36849ab48fe'

const createdAccessCode = await seam.accessCodes.create({
  device_id: deviceId,
  name: 'my time-bound code',
  starts_at: '2025-01-01T16:00:00Z',
  ends_at: '2025-01-22T12:00:00Z',
  use_backup_access_code_pool: true,
})

console.log(createdAccessCode)
Response: 
{
  "access_code_id": "f863cb36-7f96-4b56-ac91-115742c31c00",
  "device_id": "6aae9d08-fed6-4ca5-8328-e36849ab48fe",
  "name": "my time-bound code",
  "appearance": null,
  "code": "8030",
  "common_code_key": null,
  "type": "time_bound",
  "status": "unset",
  "is_scheduled_on_device": false,
  "starts_at": "2025-01-01T16:00:00.000Z",
  "ends_at": "2025-01-22T12:00:00.000Z",
  "pulled_backup_access_code_id": null,
  "is_backup_access_code_available": true,
  "created_at": "2023-10-19T11:41:27.273Z",
  "errors": [],
  "warnings": [],
  "is_managed": true,
  "is_external_modification_allowed": false
}

​
2. Detect when an access code has failed to program

When you receive an access_code.failed_to_set_on_device event through your Webhook, or notice a failed_to_set_on_device error on the access code object, that means that the access code has failed to program. You can retrieve a backup access code to use instead.

​
3. Confirm the availability of a backup access code

To confirm that a backup access code is available for retrieval, check the is_backup_access_code_available property on the access code by inspecting the response from Get Access Code or List Access Codes. If the backup code pool has been exhausted, this property returns false.
Note that we only support pulling backup codes for time_bound codes at this time.
Request: 
const accessCode = await seam.accessCodes.get({
  access_code_id: 'f863cb36-7f96-4b56-ac91-115742c31c00',
})

console.log(
  'Is backup access code available: ' +
    accessCode.is_backup_access_code_available,
)
Response: 
Is backup access code available: true

​
4. Retrieve a backup access code

To retrieve a backup access code for an access code, include the access_code_id in the Pull Backup Access Codes request. In the response, you receive the new backup access code. Be sure to share the new backup PIN code with the user of the original access code. Upon executing this action, Seam performs the following additional actions:
  • Mark the backup access code as pulled ("pulled": true), meaning that it has been removed from the pool.
  • Associate the backup access code with the original access code, ensuring that any future requests to the Pull Backup Access Code request return the same backup access code.
  • Update the ends_at date for the backup access code to match that of the original access code.
  • Attempt to refill the backup access code pool with a new backup code.
Request: 
const backupAccessCode = await seam.accessCodes.pullBackupAccessCode({
  access_code_id: 'f863cb36-7f96-4b56-ac91-115742c31c00',
})

console.log(backupAccessCode)
Response: 
{
  "access_code_id": "284cc090-5d89-4e9d-a4ed-518c6cb68d99",
  "device_id": "6aae9d08-fed6-4ca5-8328-e36849ab48fe",
  "name": "Backup 284cc090-5d89-4e9d-a4ed-518c6cb68d99 (Seam)",
  "appearance": {
    "name": "Backup 284cc090-5d89-4e9d-a4ed-518c6cb68d99 (Seam)",
    "last_name": "284cc090-5d89-4e9d-a4ed-518c6cb68d99 (Seam)",
    "first_name": "Backup"
  },
  "code": "1275",
  "common_code_key": null,
  "type": "time_bound",
  "status": "set",
  "starts_at": "2023-10-19T11:50:21.092Z",
  "ends_at": "2025-01-22T12:00:00.000Z",
  "is_backup": true,
  "is_backup_access_code_available": false,
  "created_at": "2023-10-19T05:07:05.369Z",
  "errors": [],
  "warnings": [],
  "is_managed": true,
  "is_external_modification_allowed": false
}

​
Troubleshooting

When you have the backup access code pool feature enabled for a device, be on the lookout for the following warnings and errors on the device:

​
Warning: many_active_backup_codes

Multiple back up codes have been pulled from the device. This usually indicates that Seam is having issues programming access codes onto the device. Check if the device is offline or if there are other issues.

​
Warning: partial_backup_access_code_pool

Seam is having trouble refilling the back up access code pool. This could result from device connection issues or from the device running out of space for new codes.

​
Error: empty_backup_access_code_pool

There are no more back up codes available in the pool. This can happen when you’ve just enabled the back up pool feature, or when all of the backup access codes have been used.

​
Supported Brands

All door locks with the access_code capability are expected to support this feature, with the exception of Salto locks.