# 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](https://docs.cronofy.com/schedule/scheduling-and-booking/selection-rules/index.md),
[Templates](https://docs.cronofy.com/schedule/scheduling-and-booking/templates/index.md), and
[booking limits](https://docs.cronofy.com/schedule/scheduling-and-booking/booking-limits/index.md),
and use the access described in
[Authorization](https://docs.cronofy.com/developers/managed-scheduling/authorization/index.md).

## Embedded
[Embedded scheduling](https://docs.cronofy.com/api-reference/managed-scheduling/embedded-scheduler/index.md)
puts the Scheduler inside your application. Your users create Scheduling
Requests through its interface, and your application
[receives updates](https://docs.cronofy.com/api-reference/managed-scheduling/scheduling-requests/webhooks/index.md)
as each one progresses.

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

- [Create a Scheduling Request](https://docs.cronofy.com/api-reference/managed-scheduling/scheduling-requests/create/index.md),
optionally
[from a Template](https://docs.cronofy.com/api-reference/managed-scheduling/scheduling-requests/create-requests-with-templates/index.md).

- [Query the Scheduling Requests](https://docs.cronofy.com/api-reference/managed-scheduling/scheduling-requests/query/index.md)
you've created.

- [Cancel a Scheduling Request](https://docs.cronofy.com/api-reference/managed-scheduling/scheduling-requests/cancel/index.md).

With [Time Selection](https://docs.cronofy.com/api-reference/managed-scheduling/scheduling-requests/integration-operations/index.md),
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](https://docs.cronofy.com/api-reference/managed-scheduling/scheduling-requests/webhooks/index.md)
as each request is booked, rescheduled, declined, or cancelled, so your
application can act on them. See
[Webhooks & workflows](https://docs.cronofy.com/developers/temporal-grid/webhooks/index.md)
for the other webhooks through a meeting's lifecycle.



---
[Read in HTML](https://docs.cronofy.com/developers/managed-scheduling/scheduling-requests/)