Integrate physical access control with Kangarootime using its partner-built Kisi integration rather than a self-serve public API
domain: help.kangarootime.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the desired integration is one of Kangarootime's listed partner integrations under its Integrations help section rather than assuming an open developer API
For access-control/door-entry use cases, use the Kisi-maintained integration documented in Kisi's product docs, since Kisi (not Kangarootime) maintains and supports that connector
For payment processing, note Kangarootime's platform-level partnership with Worldpay for Platforms/Payrix Pro rather than building custom payment API calls
Contact Kangarootime support (support@kangarootime.com) to request enabling a specific listed integration for the account
Treat 'API-first' marketing language as describing Kangarootime's internal architecture, not confirmation of an open self-serve developer API
Known gotchas
The Kisi <> Kangarootime integration is explicitly partner-built and maintained by Kisi, so support requests for that connector should go to Kisi, not Kangarootime, and vice versa
Kangarootime markets itself as 'API-first' for its own internal integrations (billing, enrollment, scheduling), which is easy to misread as an open public API for external developers
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?