# Custom Headers

Sometimes it is necessary to identify an answer in connection with the request.

For example, you are on a web-page that displays client *account A* information, and you are sending a request in the context of this client *account A*. While your are waiting for the response - which might take "some" time - the user moves on to another client *account B.*

If the response arrives it'll contain the data requested for account A, and you don't want to process this response data any longer because the context has moved to account B.

{% hint style="info" %}
For such use-case, you can use customer headers, which are passed-though from the service. Customer headers start with **`x-custom`**, and whatever you send in the request, it will be in the related response.
{% endhint %}

For example:

```http
GET {{host}}/Docs/query?key=*&UserId=*&Context=*
Authorization: Basic {{basicToken}}
x-custom-boomiaccount: Account A


HTTP/1.1 200 OK
...
x-custom-boomiaccount: Account A
{ ... }
```


---

# 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://services.markusschmidt.pro/mspro.services/general-information/custom-headers.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.