> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/restapi-integracje-z-zewnetrznymi-systemami/platformowy-naglowek-z-identyfikatorem-tenanta.md).

# Platform header with tenant identifier

## Introduction <a href="#platformowynaglowekzidentyfikatoremtenanta-wstep" id="platformowynaglowekzidentyfikatoremtenanta-wstep"></a>

It is possible to enable a platform mechanism that will add a header with the tenant identifier (partnerId, bank settlement number) to all REST requests from scripts and script tasks.

Configuration

The following properties are used to enable the mechanism, to be configured in the webforms applications (for scripts, depending on the deployment environment, in application.yml or in webforms.xml) and in process-handler-executor-camunda (for script tasks):

<table><thead><tr><th width="254">Property</th><th width="406">Description</th><th>Default value</th></tr></thead><tbody><tr><td>script-service.tenant.interceptor.enabled</td><td>A boolean value indicating whether the header-adding mechanism should be enabled.</td><td>false</td></tr><tr><td>script-service.tenant.interceptor.header-name</td><td>A string specifying the header name.</td><td>x-tenant-id</td></tr></tbody></table>

For the mechanism to work properly:

* **for the script** - the request on which it will be invoked must have a defined partnerId variable; its value is passed to the header,
* **for the script task** - the header receives the Tenant ID value for which the process instance is started.

Nothing else needs to be done from the script/handler itself.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/restapi-integracje-z-zewnetrznymi-systemami/platformowy-naglowek-z-identyfikatorem-tenanta.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.