> 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/actions/apis/apis-list/set-api-key.md).

# Set Api Key

This is a pre-built action located under the **APIs List**. The functionality of this action in Avo Assure is to set an API key for authenticating requests.

### Syntax

**Input Value:** `<Key>;<Value>;<Add to>`

| Argument  | Description                                                    |
| --------- | -------------------------------------------------------------- |
| \<Key>    | Enter the name of the API key (e.g., x-api-key, Authorization) |
| \<Value>  | Provide the value associated with the API key                  |
| \<Add to> | Provide the location to add the API key header                 |

#### Output Value

| Argument | Description    |
| -------- | -------------- |
| N/A      | Not Applicable |

**Example**

**Adds an API key to the API request for authentication.**

The **Set Api Key** action takes the value from the Input Value column **(e.g., Authorization;JWT \<token>;Header)** and attaches the specified key and value to the defined location in the request Header.

{% hint style="info" %}
**Note:** Provide a space between "**JWT**" and "**access token**".
{% endhint %}

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FGZH0E5NZSX1ktu9UfDEG%2Fimage.png?alt=media&amp;token=701102c5-0a79-4ab4-afeb-7d256b72dbb0" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/apis/apis-list/set-api-key.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.