Update Multiple Linked Access Codes

Updates access codes that share a common code across multiple devices.

Specify the common_code_key to identify the set of access codes that you want to update.

See also Update Linked Access Codes.

POST /access_codes/update_multiple

JavaScript

Seam SDK

await seam.accessCodes.updateMultiple({
  ends_at: "2025-06-22T05:05:47.000Z",
  starts_at: "2025-06-18T19:14:13.000Z",
  name: "My Updated Linked Access Code",
  common_code_key:
    "auto_set_by_create_multiple_550e8400-e29b-41d4-a716-446655440000",
});

/*
// void
*/

200

{
  "ok": true
}

Authorizations

client_sessionclient_session_with_customerpat_with_workspaceconsole_session_with_workspaceapi_key

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

common_code_key · string · required

Key that links the group of access codes, assigned on creation by /access_codes/create_multiple.

ends_at · string

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.

name · string

Name 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).

starts_at · string

Date and time at which the validity of the new access code starts, in ISO 8601 format.

Response

200

application/json

OK

ok · boolean · required