Create a time-bound guest access code across multiple lock brands using the Seam API
domain: docs.seam.co · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with a Seam API key against https://connect.getseam.com
Confirm the target device supports online access-code programming (capability flags vary by whether the device supports online vs. offline codes)
Create a timebound access code with a set of ISO 8601 start/end timestamps via the access-codes endpoints documented in the Smart Locks capability guide
Retrieve lock.locked / lock.unlocked events afterward and check the method field (keycode) plus access_code_id and access_code_is_managed to confirm the guest actually used the Seam-issued code
Delete or let the code expire per its schedule, and confirm removal by re-listing the device's access codes
Known gotchas
Seam distinguishes "managed" codes (created via Seam) from codes programmed directly on the device outside Seam — access_code_is_managed will be false for the latter, which matters for audit trails
Offline-capable devices (e.g., some igloohome or TTLock hardware) handle codes differently than fully online devices — check the specific brand's integration guide under Seam's device-and-system-integration-guides before assuming uniform behavior
Event method values (keycode, manual, remote, automatic, unknown) require checking multiple related properties (access_code_id, is_via_bluetooth, is_via_nfc) to fully disambiguate how a door was actually operated
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?