Unlock a door on demand through the Genea Access Control API
domain: apidocs-accesscontrol.getgenea.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with a Global API Key
Identify the target door within the correct location_uuid
Call the door unlock/momentary-release endpoint for that door
Handle standard Genea HTTP status codes (403 for invalid/insufficient-permission key, 404 for unknown door)
Confirm the unlock by checking the resulting entry in the audit event list
Known gotchas
A 403 can mean either an invalid API key or a key that lacks permission for that specific resource — the error body must be inspected to tell which
Doors, Control Points, and Monitor Points are distinct object types; sending an unlock call to a Control Point ID instead of a Door ID will not behave as expected
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?