Kisi API
Kisi ships public, interactive API docs with webhooks and documented rate limits, and customers can hold API keys. Sandbox and SDK access must be requested, and commercial access runs through a quote, so integration work starts with a conversation.
Frequently asked questions
Kisi scores C on Supergood's API Report Card. Kisi ships public, interactive API docs with webhooks and documented rate limits, and customers can hold API keys. Sandbox and SDK access must be requested, and commercial access runs through a quote, so integration work starts with a conversation.
Kisi has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Kisi is a cloud based physical access control platform that manages doors, readers, credentials, and unlock events for offices, coworking spaces, and multi tenant buildings.
Real estate and workplace operations buyers: office tenants, coworking and flex space operators, property managers, and multi site employers who need keyless entry, credential lifecycle control, and an audit trail of who opened which door and when. Teams use Kisi to provision and revoke door access as employees and members join or leave, to issue mobile and card credentials, to set schedules and calendars for when doors unlock, and to review unlock events for security and compliance.
Kisi is an established cloud access control vendor with published hardware, mobile apps, and public review profiles referenced from its own pricing page, but no sourced customer counts or market share figures are publicly available, so its footprint is best described qualitatively as a recognized mid market player rather than a category default.
Kisi holds the physical access record for a building: door and place inventory, controller and reader configuration, user and group membership, credential assignments, access rights and schedules, calendars, and the chronological unlock and event log showing which person opened which door at which timestamp.
The platform is cloud native and the developer surface looks modern in shape: HTTPS only requests, JSON payloads, an interactive reference where a token can be pasted to execute calls, documented 429 behavior with exponential backoff guidance, and published rate limits of 5 requests per second per authenticated user and 5 per second per IP for unauthenticated traffic.
Common alternatives include Brivo, Openpath, Envoy. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Not that we could find. There is no official Kisi MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Kisi doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.