Authorization
Read as MarkdownAvailability queries and calendar events work on calendar accounts. Most
endpoints take an access_token for the account, or the account’s sub, so
your application first needs authorization to the calendars it works with.
How Cronofy itself connects to each calendar service, and what calendar
administrators need to set up, is covered in
Connect with Cronofy.
| Method | When it fits |
|---|---|
| Individual Connect | Each of your users connects their own calendars through an OAuth 2.0 flow. The default for most applications. |
| Enterprise Connect | An administrator grants access to calendars across their domain, including resources such as meeting rooms, so users don’t authorize one by one. |
| Organizational Unit with impersonation | Your users’ calendars are already connected to a Cronofy Organizational Unit. An Internal Application acts for each member by passing their sub in the Cronofy-Impersonate header. |
| Application authentication | Endpoints that aren’t tied to one user, such as Availability queries across accounts, Bookable Events and Smart Invites, take the application’s client_secret. |
Whichever method you use, Calendar Access Modes and Permissions decide how much of each calendar your application can read and change.
Where there’s no calendar to connect, Application Calendars give your application an account of its own.