Issue a virtual key / visitor pass through the ButterflyMX API
domain: apidocs.butterflymx.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate via OAuth 2.0 against the Sandbox or production environment
Review the Virtual Keys (visitor passes) guide for the request schema
Call the endpoint to create a time-bound visitor pass tied to a unit/resident
Optionally set a PIN for the visitor via the Manage Resident PIN endpoints
Verify the pass appears correctly in the resident's ButterflyMX app and in Access/Call Logs
Known gotchas
Visitor passes and Manage Resident PIN are separate endpoints even though both grant entry — confusing the two produces a pass that doesn't respect PIN-specific expiration rules
Sandbox-issued visitor passes do not carry over to production; separate credentials must be issued once the app moves off Sandbox
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?