> 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-header-template.md).
# Set header template
This is a pre-built Action located under the **APIs List**. The functionality of this Action in Avo Assure is to populate the input field with values from the header defined in the stored template and apply them to the API request. This enables required headers to be set dynamically for further use during API execution.
## **Syntax**
**Input Value**: `N/A`
| Argument | Description |
| -------- | -------------- |
| N/A | Not Applicable |
**Output Value**: `N/A`
| Argument | Description |
| -------- | -------------- |
| N/A | Not Applicable |
### **Example: Setting a Header Template for a APIs Request**
In this example, we are explaining how to apply a predefined header template to a API request during API testing.
* **Action**: Set Header Template
* **Input Value**: N/A
* This action does not require any input value. It applies a predefined header template to the API request for subsequent API execution.
* **Output Value:** N/A
* **Logical Explanation**: The **Set header template** action does not require any input value. The action applies the configured header template to the API request, ensuring that the required headers are included for the API call.
---
# 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-header-template.md?ask=&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.
