Waymark / Routes / developer.remotelock.com
Generate and revoke guest keyless-entry codes via the RemoteLock API
domain: developer.remotelock.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Email sales@remotelock.com to get API access enabled on your account (docs are public, but activation is gated). Authenticate via OAuth2 (Authorization Code or Client Credentials grant). POST to /access_persons with type access_user and generate_pin:true to auto-generate a PIN tied to a guest/reservation. Associate the created access person with the correct lock/device and validity window (check-in to check-out dates). Call PUT /access_persons/:id/deactivate at or after checkout to revoke the code.
Known gotchas API access itself is gated behind a sales conversation even though the reference docs are public — budget onboarding time before development. Deactivation is a manual/API-triggered step, not automatic — tie it to your PMS's checkout event to avoid stale active codes.
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