Grant a registered user door access via the RemoteLock API
domain: developer.remotelock.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Email sales@remotelock.com to request API access for the account, then create a new OAuth Application in the developer portal to get a Client ID/Secret
Exchange credentials for an access_token via OAuth2 (Authorization Code grant for user-delegated access, or Client Credentials grant for server-only integrations) against connect.remotelock.com/oauth/token
Fetch the list of devices/locks on the account to identify the target lock
Create or find the access person (user) record, then create a separate access grant tying that person to the specific device
Use the returned refresh_token to obtain new access tokens without re-prompting the user once the initial token expires
Known gotchas
API access must be requested by email before the OAuth Application option becomes available in the portal
Access tokens expire in about 7200 seconds (2 hours), so a refresh flow is required for any long-running integration
Granting access is a two-step process (create/find the access person, then create the access grant) — there is no single unlock-by-user call
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?