# Header

## Description

Header can be read on Action, which will be received as part of the client request.

## Example use case

* **Content Negotiation**: The "Accept" header allows the client to specify the media types it can understand, enabling the server to send an appropriate response format. For instance, a client can request JSON or XML data based on its capabilities.
* **User-Agent Information**: The "User-Agent" header provides information about the client's software, enabling the server to tailor the response according to the capabilities or constraints of the client.
* **Tracking and Analytics**: Clients can send headers containing tracking information or analytics data, helping the server collect insights about how its resources are being used.

## How to use

1. Open the **Header** tab.
2. For each Action and Method, Headers can be added, edited or deleted.
3. The following fields are available:
   * **Type**: HTTP Header to read from (example: `Content-Type`)
   * **Value**: Default value of the header if the client request doesn't provide one (example: `application/json`) ![](/files/OrDv3HA1YGcvErJqhaMe)


---

# 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.emobiq.com/emobiq-server/002-api/005-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.