- Connects locks, thermostats, switches and leak sensors
- Commands reach the device in seconds, with the outcome back
- Locks keep their codes and schedules when the internet is down
Your buildings, one API. Hubs, intercoms and access control, connected to your software. Open the front door, give a cleaner a code for Thursdays, or react to a sensor the moment it fires, through one secure API.
POST /v1/hubs/1key-xfy2-nmf4-5xwp/devices/7/commands {"key": "lock", "value": false} → 202 {"channel": {"key": "lock", "desired": false, "status": "pending"}}
type sensor.triggered kind leak at 2026-10-02T14:03:11Z
1key hardware covers a building from the entrance to the suite, and every piece answers to the same API, keys and events.
The platform acts on physical spaces, so every layer assumes something else could fail.
An OpenAPI contract, examples in curl, JavaScript, Python and Elixir, and the whole reference as plain Markdown at /llms.txt, ready for Claude, Cursor or any coding assistant.
# Follow a building's events
cursor = None
while True:
page = requests.get(f"{API}/hubs/{hub}/events",
params={"after": cursor, "wait": 30},
headers=auth).json()
for event in page["data"]:
handle(event)
cursor = page["next_cursor"]
Hubs, intercoms and access control are available today. Cameras join the same API next.