Provision a new user and grant them lock access using the Kisi 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
Generate a personal or organization API key from the Kisi dashboard under Account settings
Follow the Quick Start guide at docs.kisi.io/platform/apis/get_started/ to authenticate requests against the interactive reference at api.getkisi.com/docs
Create or invite a user resource, then assign that user to a group or directly to a lock's access rights per the user-provisioning integration guide
Confirm the grant by querying the user's current access rights back from the API
Handle 429 Too Many Requests responses with exponential backoff, since Kisi caps authenticated calls at 5 requests per second per user
Known gotchas
Kisi's API has no version number and is documented as backwards-compatible by default — breaking changes are announced via a Developer Newsletter rather than a versioned endpoint, so subscribe to it
Rate limits are enforced per user (5 req/s) for authenticated calls and per IP (5 req/s) for unauthenticated calls — shared service accounts can hit limits faster than expected
The API surface spans 30+ resource types; consult the interactive reference for the exact current field names rather than assuming REST conventions
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?