> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/utilities/authorization.md).

# Authorization

The **Authorization** feature in Avo Assure generates a token used to authenticate API requests, such as creating or validating verticals, managing users and projects, and handling SSO role mappings. This token acts as a temporary digital credential and remains valid only for a specific duration (for example, 1 day or 1 week).&#x20;

## Key Capabilities

The Authorization Token Enables You To:&#x20;

* **Secure API Access**: Prevent unauthorized users from performing sensitive actions.&#x20;
* **Enable Access**: Allow to perform tasks directly via API (such as creating users or projects).&#x20;
* **Manage Session Duration**: Control how long external access remains valid through configurable expiry settings.&#x20;

## This Article Contains the Following Module

[Prerequisites](#prerequisites)\
Prerequisites for Authorization in Avo Assure.&#x20;

[Generating an Authorization Token](#generating-authorization-token)\
Steps to generate an Authorization Token in Avo Assure.&#x20;

[Example: Creating a Vertical in Avo Assure](#example-creating-a-vertical-in-avo-assure)\
Steps to use the generated token to create a new Vertical in Avo Assure.&#x20;

## Prerequisites

The following requirements must be fulfilled before you generate an authorization token:

* **Active Account**: You must have a valid and active Avo Assure user account.&#x20;
* **Project Creation**: You must have an active project created in Avo Assure to work on Webservice automation.&#x20;
* **Valid APIs**: You should have the valid Avo Assure APIs.

## Generating Authorization Token&#x20;

To generate a new API token, perform the following actions:

1. On the **Home** page, select the **Utilities**.
2. Select the **Authorization** tab to generate the **Auth Token**.&#x20;
3. Locate the **Select the token expiry** dropdown and choose the desired expiration (such as, 1 Day or 1 Week).
4. Select the **Generate Auth Token** to create a new alphanumeric token, which appears in the Generated Token field.
5. Select the **Copy to Clipboard** to copy the token for use in your API client.

<figure><img src="/files/DeBMZ4G5QoDhzXc2LZNv" alt=""><figcaption></figcaption></figure>

### Example: Creating a Vertical in Avo Assure

To apply the generated token in an API client, perform the following actions:

1. On the **Home** page, select the **Design Studio** button. The **Element Repository** page opens.
2. Create a new folder by clicking on the **Create Folder** (**+**) icon and then create a repository by selecting **Webservice** as the application type.&#x20;

{% hint style="info" %}
To learn more about **Creating a folder** and **Repository** for Webservice, [click here](/avo-assure/avo-assure-supported-technologies-for-automation/webservice-automation/creating-webservice-element.md).
{% endhint %}

3. Select **POST** as the request method from the **Select** dropdown.
4. Enter the **Avo Assure APIs URL** in the **Enter URL** box.
   * **URL**: <https://apitestlab.avoautomation.com/auth/users/>

<figure><img src="/files/RIdMaqK0equhftW2PafH" alt=""><figcaption></figcaption></figure>

5. Select the **Header** and **Body** tab and enter the following details:

<details>

<summary><strong>Header</strong></summary>

1. Enter the header details in the **Header** tab.

<figure><img src="/files/f5FO6O2Bk9V32wdSNkTl" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Body</strong></summary>

1. Enter the body details in the **Body** tab.

<figure><img src="/files/798JhrkuneRFJaifkutl" alt=""><figcaption></figcaption></figure>

</details>

6. Select the **Authorization** tab and select the **Bearer Token** from the **TYPE** dropdown.
7. Paste the generated auth token into the Token field.

{% hint style="info" %}
To learn more about **Generating Authorization Token**, [click here](#generating-authorization-token).
{% endhint %}

<figure><img src="/files/KwZ5mQe77WJAPS6oD745" alt=""><figcaption></figcaption></figure>

8. Select the **Save** and **Send** button to save the request details and execute the API.
9. Select **Response** tab to view the **Header** and **Body** response from the system.

<details>

<summary><strong>Body</strong></summary>

The **Body** tab displays the response returned by the server. The content is displayed in JSON format.

<figure><img src="/files/vx4mw3nQYQ3J0CMqy7n3" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Header</strong></summary>

The **Header** tab displays the **HTTP status code**, **Server**, **response time**, **Content-Type**, and **Length**.

<figure><img src="/files/PZomvYnBK2IAvzNhqtg7" alt=""><figcaption></figcaption></figure>

</details>

{% hint style="info" %}
To learn more on **Webservice Automation**, [click here](/avo-assure/avo-assure-supported-technologies-for-automation/webservice-automation.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/utilities/authorization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
