1KEY Platform
Docs Developer portalPortal
The 1key platform

We make
hardware simple.

Your buildings, one API. Connect the devices in your buildings to your software. Unlock a door, change a temperature, or react to a sensor the moment it fires, through one secure API.

Read the docs Get API access
Unlock a door 
POST /v1/hubs/1key-xfy2-nmf4-5xwp/devices/7/commands
{"key": "lock", "value": false}

→ 202 {"channel": {"key": "lock", "desired": false, "status": "pending"}}
Event, as it happens 
type   sensor.triggered
kind   leak
at     2026-10-02T14:03:11Z
/ Act Send commands to locks, thermostats and switches. Each one goes straight to the device in the building, and you get the outcome back.
/ React Receive door, sensor and connection events from every building you manage, in order and as they happen.
/ Control access Give each system its own key with only the permissions it needs, and revoke any key in one click.
How it works

From the building to your software.

  1. 1 Buy and install Order 1key hardware from us and install it in the building. Add each device to one of your sites in the developer portal by the Serial on its label.
  2. 2 Connected securely Every device holds its own certificate and talks to the 1key cloud over an encrypted connection. The cloud carries messages; device state stays in the building.
  3. 3 Built into your software Your servers call the 1key API with scoped keys: list devices, send commands, follow events. One integration covers every building.
Built for

Teams that run software for buildings.

Property management platforms Let staff and residents act on doors and climate from the tools they already use.
Resident and amenity apps Open the right door at the right time, and show what's happening in the building live.
Building operations Catch leaks, low batteries and offline devices before they become a call.
Security

Built for doors that matter.

The platform acts on physical spaces, so every layer assumes something else could fail.

Every device has its own identity
Each device generates its own key and never shares it. No fleet-wide passwords.
Device state stays in the building
The cloud carries commands and events. It doesn't keep a copy of your building.
Least-privilege API keys
Keys carry only the scopes you grant, are stored as hashes, and stop working the moment you revoke them.
Ownership checked on every request
A key can reach only its own organization's devices. Everything else looks like it doesn't exist.
For developers

Docs your AI assistant can read.

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.

Read the docs Build with AI 
# 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"]

Start with 1key hubs.

Hubs and the locks, thermostats, switches and sensors they connect come first. More building systems will join the same API.

Get API access Developer portal