Scheduling Requests

A Scheduling Request is how Cronofy manages a meeting from start to finish. It captures who needs to meet and the booking flow to follow, then Cronofy runs it: finding times, booking, rescheduling and cancelling.

Scheduling Requests can be created through the API, or by your users through the Scheduler. Either way they follow the rules set for the Organizational Unit, such as Selection Rules, Templates, and booking limits, and use the access described in Authorization.

Embedded #

Embedded scheduling puts the Scheduler inside your application. Your users create Scheduling Requests through its interface, and your application receives updates as each one progresses.

Headless #

Your application can work with Scheduling Requests directly over the API:

• Create a Scheduling Request, optionally from a Template.
• Query the Scheduling Requests you’ve created.
• Cancel a Scheduling Request.

With Time Selection, your application can list a Scheduling Request’s available times and book one itself, rather than sending the person to a booking page. This works for requests that only need a time to be chosen.

Reacting to changes #

Cronofy sends Scheduling Request webhooks as each request is booked, rescheduled, declined, or cancelled, so your application can act on them. See Webhooks & workflows for the other webhooks through a meeting’s lifecycle.