# Request authorization

> **PRERELEASE**

#### Description
When Business Connect is enabled for your application, you may request the
ability to access other calendars through the user's account.

This is achieved by adding an additional `delegated_scope` parameter to your
[Account Authorization request](/developers/api/authorization/request-authorization/index.md).

This will issue you a short-lived, single-use `code` that you will be able to
exchange for an `access_token` and `refresh_token` for the user, along with
enabling your application to make [Delegated Authorization requests](/developers/api-alpha/business-connect/delegated-authorization/index.md)
using their account.

#### Example request URL
The parameters are encoded in the querystring as specified in <a href="https://www.rfc-editor.org/rfc/rfc6749#appendix-B">appendix B of RFC 6749</a>. Additional linebreaks are added to the request's path for clarity.

```
https://app.cronofy.com/oauth/authorize
    ?response_type=code
    &client_id={CLIENT_ID}
    &redirect_uri={REDIRECT_URI}
    &scope={SCOPE}
    &delegated_scope={DELEGATED_SCOPE}
    &state={STATE}
```

#### Request URL parameters
In addition to the [standard authorization parameters](/developers/api/authorization/request-authorization/index.md),
you must specify:

##### `delegated_scope` *(required)*

The scope of delegated privileges you want the eventual `access_token` to grant for other accounts. One of the following scopes must be requested:

- `free_busy`

- `read_only`

`free_busy` will allow your application to access availability information for
other calendar accounts. `read_only` will allow your application to access the
schedule of other calendar accounts.



---
[Read in HTML](/developers/api-alpha/business-connect/request-authorization/)