Define recurring availability rules and generate a real-time scheduling link with the Cronofy API
domain: docs.cronofy.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Grant at least the read_free_busy scope (or broader) for each participant you intend to include in an availability calculation.
Create or update an Availability Rule per person/resource via the Availability Rules endpoint to capture their regular recurring working hours, distinct from one-off available periods.
Set the managed_availability flag on a participant in an Availability Query or Real-Time Scheduling request so their stored Availability Rules are applied dynamically rather than passing ad hoc available periods each call.
Call the Availability Query endpoint with all participants and the required duration to get common free slots across their calendars.
Alternatively call Real-Time Scheduling to get back a hosted URL where the end user picks from live-computed available slots, rather than building your own slot picker UI.
Known gotchas
Availability Rules (recurring weekly patterns) and Available Periods (one-off slot options) are separate concepts in Cronofy's model — mixing them up leads to either missing recurring hours or over-constraining one-time queries.
Real-Time Scheduling responses embed the underlying availability-query parameters used, so if your rules or managed_availability flags are wrong, the hosted picker will silently reflect the same wrong availability rather than erroring.
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?