Configure a Nylas v3 Scheduler booking page (configuration) for external guests to book time
domain: developer.nylas.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST /v3/grants/{grant_id}/scheduling/configurations with the settings for the page: participant calendars to check, event duration/details, and booking rules.
Choose public (Nylas-hosted under a book.nylas.com slug) or private (session-authenticated) hosting for the resulting configuration_id.
Set scheduler.rescheduling_url and scheduler.cancelling_url via an Update Configuration call if you want guests routed to a custom cancel/reschedule experience instead of the default one.
Customize confirmation behavior with confirmation_redirect_url and the email_template.booking_confirmed title/body fields.
Embed the page using the configuration_id in the Scheduler component/widget, or link directly to the hosted page slug for public configurations.
Known gotchas
Private configurations require a valid session id on every Availability/Bookings call — a public page's simpler unauthenticated flow won't work if you've configured it private, and vice versa.
Hosted Scheduling Pages support pre-filling fields via URL query parameters, but those values are guest-editable defaults, not enforced/locked values — don't rely on them for access control.
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?