Organizational Unit Authorizations ALPHA
Organizational Unit authorizations allow developers of external applications to have access to an Organizational Unit to perform scheduler operations via APIs without having to implement OAuth authorization flows.
For example, if you are developing an application, you can use an Organizational Unit authorization to access details for all members of your company’s Cronofy Organizational Unit and generate scheduling requests for them.
Authorization #
For your application to access an Organizational Unit, you need to generate an Organizational Unit token. This can be done via the normal authorization endpoint , but instead requesting the scope organizational_unit_scheduler.
This scope defines that the external application has been authorised access to an Organizational Unit but that this access is only scoped to the Scheduler and no further operations. This means it is limited to only perform Scheduler requests and cannot be used to perform other requests.
You can additionally authenticate as an account linked to the Organizational Unit by passing the sub value in the Cronofy-Impersonate header:
POST /v1/scheduler_requests HTTP/1.1
Host: {data_center_url}
Authorization: Bearer {API_KEY}
Content-Type: application/json; charset=utf-8
Scope: organizational_unit_scheduler
Cronofy-Impersonate: acc_5ba21743f408617d1269ea1e
{
...
}