# Get header

This is a pre-built action located under the **WebService List** Element. The functionality of this action in Avo Assure is to fetch the response header after executing a webservice request and save the result in the dynamic variable.

### **Syntax**

**Input Value:** `<Header Key>`

{% hint style="info" %}
**Note:**

* If no value is entered in the input column, the entire response header is saved in the output variable.
* If a specific header key is provided, only the value of that key is retrieved.
  {% endhint %}

| Argument                 | Description                                         |
| ------------------------ | --------------------------------------------------- |
| \<Header Key> (Required) | Enter the specific key name of the response header. |

**Output Value**

| Argument                       | Description                                                                |
| ------------------------------ | -------------------------------------------------------------------------- |
| \<Dynamic Variable> (Required) | This dynamic variable it holds the header or value.                        |
| \<Dynamic Variable> (Optional) | This dynamic variable holds the execution status as **True** or **False.** |

**Example**

**Retrieves a Specific Response Header from a Web Service**

The **Get header** action takes the value from the Input Value column (e.g., Content-Type) and fetches the corresponding header from the response of the executed WebService request. The retrieved value is stored in the **{HeaderValue}** variable as **application/json.**

<figure><img src="/files/7DOdlDpORFH9XNwz9d48" alt=""><figcaption></figcaption></figure>


---

# 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.avoautomation.com/avo-assure/actions/web-service-operations/web-service-list/get-header.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.