Skip to main content
After you’ve created an Access Grant, circumstances change — a guest extends their stay, a contractor’s scope expands to a new building, or a reservation is cancelled. This page covers how to update or delete an Access Grant to handle these situations.

​
Updating an Access Grant

Use access_grants.update when you need to change when or where a person has access. Common scenarios include:
  • Extended stay: A hotel guest extends their checkout from Friday to Sunday — update ends_at.
  • Early access: A contractor needs to start a day earlier — update starts_at.
  • Scope change: A resident moves from Unit 101 to Unit 205 — update device_ids, space_ids, or acs_entrance_ids.

​
Updating the Schedule

Pass starts_at and/or ends_at to change the access window. The new schedule applies to all access methods under the grant. 
# Guest extended their stay — push checkout to Sunday
seam.access_grants.update(
    access_grant_id="ef83cca9-5fdf-4ac2-93f3-c21c5a8be54b",
    ends_at="2025-07-18T11:00:00.000Z",
)

​
Updating Resources

Pass device_ids, space_ids, or acs_entrance_ids to change where the person has access. For example, if a resident moves units, update the grant to point to the new space instead of deleting and recreating it. 
# Resident moved from Unit 101 to Unit 205
seam.access_grants.update(
    access_grant_id="ef83cca9-5fdf-4ac2-93f3-c21c5a8be54b",
    space_ids=["b0c5d5e0-7f0a-4f1b-8e3d-unit-205-space"],
)

​
Re-issuance After an Update

When you update an Access Grant, Seam needs to re-program the credentials on the affected devices. During this process, each access method temporarily becomes invalid.

​
What happens to each access method

  1. Seam emits an access_method.revoked event and sets is_issued to false. The credential is no longer valid on the device.
  2. Seam re-programs the credential with the updated schedule or resources.
  3. Once the credential is active again, the next step depends on the mode:
ModeWhat happensEvent
PIN codeThe code value stays the same. Seam updates the valid time window on the lock automatically.access_method.reissued
Mobile keySeam updates the credential automatically.access_method.reissued
Cloud keySeam updates the credential automatically.access_method.reissued
CardThe physical card must be re-encoded with the new credential.access_method.card_encoding_required, then access_method.reissued after encoding
For cards, you’ll need to re-encode the card before the updated credential takes effect. Plan for this if your workflow relies on physical cards — the guest will need to visit the front desk.

​
Listening for re-issuance events

Use webhooks or poll access_methods.list to track when access methods become valid again after an update:
  • access_method.revoked — The credential has been invalidated and is being re-programmed. The access method’s is_issued is false.
  • access_method.card_encoding_required — (Cards only) The new credential is ready but needs to be encoded onto the physical card.
  • access_method.reissued — The credential is active again. The access method’s is_issued is true.

​
Deleting an Access Grant

Delete an Access Grant when a person’s access should end entirely — for example, when a guest checks out, an employee is offboarded, or a contractor’s engagement ends. Deleting the grant removes all access methods under it at once. 
# Guest checked out — revoke all access
seam.access_grants.delete(
    access_grant_id="ef83cca9-5fdf-4ac2-93f3-c21c5a8be54b"
)
Seam emits an access_grant.deleted event and an access_method.deleted event for each access method that was removed.
To revoke a single access method while keeping the rest active (for example, disabling a lost key card but keeping the guest’s PIN code), use access_methods.delete instead.

​
Delete vs. Update

ScenarioAction
Guest checks out, employee offboards — all access should endDelete the Access Grant
Guest extends stay, schedule changesUpdate starts_at / ends_at
Person moves to a different unit or buildingUpdate device_ids, space_ids, or acs_entrance_ids
One credential is lost but the person still needs accessDelete the access method, not the grant