Configure a scheduled automatic unlock (and exceptions) for a Kisi-controlled door instead of a one-off remote unlock
domain: docs.kisi.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the target door (lock) or group in Kisi that should follow an automatic unlock schedule
Create an unlock schedule object with consequence: 'unlock', scheduleable_type of GROUP or LOCK, the relevant scheduleable_id, and type single_event or recurring_event with starts_at/ends_at
Enable the schedule (enabled: true) so Kisi begins auto-unlocking the door during the configured windows
Add unlock schedule exceptions (single, recurring, or holiday type) to override the base schedule and re-lock the door on specific dates, such as holidays
Verify behavior in the Kisi dashboard or via the API by checking the door's current lock state during and outside the scheduled window
Known gotchas
This is a distinct feature from a real-time/manual remote unlock call — building a cron job that calls 'unlock now' repeatedly is not the same as, and less reliable than, a native unlock schedule
Exceptions can both add and remove unlocked time — a holiday exception is commonly used to force a door to stay locked during a scheduled unlock window
The full JSON schema for schedule objects lives behind Kisi's JS-rendered API reference (api.kisi.io/docs) — confirm exact field names there before coding against them
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?