Remotely unlock a Kisi-connected door via the Cloud Unlocks API
domain: docs.kisi.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with your organization's admin API key
POST to /locks/{id}/unlock with the target lock's ID
Optionally include context.location (latitude/longitude) if the lock has a geo-fence restriction, or lock.proximity_proof if it has a proximity restriction
Read the 200 OK 'Unlocked!' response to confirm the command was received
Check the organization's audit log afterward, since cloud-unlock events are attributed to the admin/API key owner, not an individual user
Known gotchas
All cloud-unlock events log as an admin action tied to the API key, so this method is unsuitable if you need per-technician audit trails
Geo-fence- or proximity-restricted locks will reject the unlock without the matching context/proximity_proof fields
The unlock's open duration is a hardware setting on the lock itself, not something the API call controls
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?