> For the complete documentation index, see [llms.txt](https://docs.parqex.com/-MUyxAVrX9S4wky8UoX6/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parqex.com/-MUyxAVrX9S4wky8UoX6/oauth/how-to-authorize-access/step-1-generate-authorization-url.md).

# Step 1: Generate Authorization URL

Sending the user to this link will redirect the user to the ParqEx website from which they may login (if they do not already have an active session) and choose whether to allow your application to connect to their ParqEx account. After the user elects to *ALLOW* or *DENY*, the user is redirect to the supplied *ENCODED\_REDIRECT\_URL*.

Which should match the format (line breaks added for clarity):

```bash
https://api.parqex.com/oauth/v2/endpoints/authorization/?
    response_type=code&
    client_id=<CLIENT_ID>&
    redirect_uri=<ENCODED_REDIRECT_URL>&
    scope=<SCOPE>&
    state=<STATE>
```

For example, with some real data (line breaks added for clarity):

```
https://api.parqex.com/oauth/v2/endpoints/authorization/?
    response_type=code&
    client_id=555555555555555555.api.parqex.com&
    redirect_uri=https%3A%2F%2Fexample%2Eorg%2F&
    scope=opendoor,closedoor&
    state==dzRBV1RxdWg5S0JWUTBhMGpEUy9NT3lGS2xjbkRsMHBDeEJDTXdPS1JpRzhlS3FFRmorOHo2SUoxZmlYb0o4dE8wRGM3Nnhwd0xNbWRIUWUvSmptM2c9PS0tSk4yM1Y2ckR1WmZCUGxjc3JBWDBhdz09--e6f508aa05569a93aaa02414c20ab808e8fbda49
```

### Available Scopes

The `<SCOPE>` param should be supplied a comma-separated list of the following abilities depending on the use-case of your application. These values are not case-sensitive.

**`OPENDOOR` -** This scope enables the integration to open the door.

**`CLOSEDOOR`** - This scope enables the integration to close the door.