# Step 2: Handle Authorization Response

Assuming the user approves the request, an authorization code is generated and sent back to your application via the query string of the *ENCODED\_REDIRECT\_URL*. If the authorization request included state, the exact same value will be returned in the authorization response.

Which follows this format (line breaks added for clarity):

```bash
GET https://example.org/?
    code=<CODE>&
    state=<STATE>
```

For example (line breaks added for clarity):

```bash
GET https://example.org/?
    code=1fe21db7d29e61a9dd90da9eef675ea8&
    state=dzRBV1RxdWg5S0JWUTBhMGpEUy9NT3lGS2xjbkRsMHBDeEJDTXdPS1JpRzhlS3FFRmorOHo2SUoxZmlYb0o4dE8wRGM3Nnhwd0xNbWRIUWUvSmptM2c9PS0tSk4yM1Y2ckR1WmZCUGxjc3JBWDBhdz09--e6f508aa05569a93aaa02414c20ab808e8fbda49
```

{% hint style="danger" %}
**Warning!** If the `state` does not exactly match the state that you are expecting, **do not continue**.&#x20;
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.beamlabs.io/oauth/how-to-authorize-access/step-2-handle-authorization-response.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.