Introducing Our Salto KS and Space Integrations

Introducing Our Salto KS and Space Integrations

This week, we’re thrilled to announce our Salto KS and ProAccess Space integrations, among our ever-growing support for physical access systems. Salto KS and Salto Space use very different deployment models—and Seam now supports both.

Salto KS

Salto KS is cloud-based, which is ideal for distributed properties and teams that need remote management and real-time updates.

Salto Space

Salto Space is an on-premises system that is preferred in hotels and buildings that require offline operation or tight integration with local systems. You connect Salto Space securely using Seam Bridge.

Flexible Credential Types

Whether you’re deploying to modern apartments or traditional hotels, Seam enables you to use the same API to issue keys, manage credentials, and simplify operations across both cloud-based and on-premises environments.

With Seam, you can issue PIN code and mobile key credentials for Salto KS users, as well as key card and mobile key credentials for Salto Space users. In addition, because Salto Space key cards require encoding, the Seam integration for Salto Space also provides user-friendly card encoding and scanning endpoints.

Get Started

We can’t wait to see what you’ll build with our Salto KS and Space integrations!

To get started:

• Salto KS system integration guide
• Salto Space system integration guide
• Access system quick start guides
• Working with card encoders and scanners

2025.05.02 Changelog

New

• Schlage real-time events: As a final step in the upgrade of our Schlage integration to their new API version, we’re adding support for real-time access code and lock/unlock events for Schlage devices. We will start rolling out these improvements over the next week, so keep an eye out!
• Ability to report SmartThings access code length constraints: We added an /access_codes/report_device_constraints endpoint that enables you to report access code length constraints for SmartThings-connected locks. Specify these constraints either as a set of supported access code lengths or as a minimum and maximum supported code length. For details, see Report Device Access Code Constraints.

Fixes

• Incorrect Lockly access code times: We corrected a time zone handling issue that was causing incorrect access code starting and ending times for Lockly devices.
• Broken link in Seam Console invitation: We corrected a broken link in the invitation email that Seam Console sends when a new team member is added to a workspace.
• Extraneous thermostat event: We corrected an issue in which an extraneous thermostat.manually_adjusted event was sent alongside a thermostat.climate_preset_activated event.
• Missing Kwikset access code date updates: We corrected an issue that was causing Kwikset access code date updates not to propagate to the affected devices.
• Salto site user deletion: We corrected an issue in our Salto KS lock integration that was causing Salto site users not to be deleted properly, which was taking up too many Salto site user slots.