Authenticate to the ProdataKey (PDK) API and remotely open a door device
domain: developer.pdk.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request API client credentials from ProdataKey (email integrations@prodatakey.com) to receive a client_id/client_secret for a registered application
Choose an auth strategy: 'clientauth' for direct client-credential authentication as a proxy user, or 'userauth' for browser-delegated OpenID Connect login
Obtain a bearer token and call the organization/system/cloud-node hierarchy to locate the target device: organizations -> systems -> cloud-nodes -> connections (controllers) -> devices
Send POST https://systems.pdk.io/{system_id}/cloud-nodes/{cloud_node_id}/devices/{device_id}/open (or /delay-open, /close, /delay-close, /force-toggle for related actions) with the bearer token
Confirm the device state changed by re-querying the device resource
Known gotchas
Device control calls require walking the full org/system/cloud-node/device hierarchy first — device IDs are not globally addressable without that context
clientauth and userauth are structurally different flows; picking userauth for a headless server integration adds unnecessary browser-redirect complexity
PDK's docs are versioned (1.0 vs 2.0) — confirm which version your registered client is provisioned against before following examples
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?