Which HTTP Requests Send the X-OpenWebUI-Message-Id HTTP Header?

[nathan-hook]

Thank you for your time,

Which requests from Open WebUI is the X-OpenWebUI-Message-Id suppose to be sent in its requests to backends?

The current documentation, as of 20260403 says:

Description: Forwards user and session information as HTTP headers to OpenAI API, Ollama API, MCP servers, and Tool servers. If enabled, the following headers are forwarded:
X-OpenWebUI-User-Name
X-OpenWebUI-User-Id
X-OpenWebUI-User-Email
X-OpenWebUI-User-Role
X-OpenWebUI-Chat-Id
X-OpenWebUI-Message-Id

However when we receive requests on /api/chat, for ollama requests or /v1/chat/completions and /chat/completions, for pipelines requests, we don't seem to be receiving the X-OpenWebUI-Message-Id.

Here is some of our output of headers sent to the urls above:

Host:"localhost:8080"
Content-Type:"application/json;charset=UTF-8"
X-OpenWebUI-User-Name:"User Name"
X-OpenWebUI-User-Id:"300a0c6e-25e6-4c1b-8f42-aef917f664c1"
X-OpenWebUI-User-Email:"email@host.com"
X-OpenWebUI-User-Role:"admin"
X-OpenWebUI-Chat-Id:"c93ef46c-8c56-4ff8-a498-d86ee4023de4"
Authorization:"Bearer neededbutnotused"
Accept:"*/*"
Accept-Encoding:"gzip, deflate, br"
User-Agent:"Python/3.11 aiohttp/3.13.2"
Content-Length:"251"

The X-OpenWebUI-Message-Id header isn't there.

Is there something that I am missing besides setting the .env ENABLE_FORWARD_USER_INFO_HEADERS=True?

Any friendly direction would be greatly appreciated.

[Classic298]

messgae id is not sent to all backens yeah

[nathan-hook]

Thanks for the reply.

Is the documentation wrong then? Or am I misreading what is stated in the documentation?

[Classic298]

sorry for the late reply - what backend are we talking about? it is certainly sent to mcpo tools but i am also pretty sure it is not sent to openai - at least it didnt used to

[nathan-hook]

So, just to be clear, it won't be sent to a pipelines request?

And if not, could we? It would be great to have that message id when handling a message via the pipelines and/or a openai api call.

FWIW, we are proxying all our open webui requests through our own api and we would love to be able to capture the message id if possible.

[OctoberRust2000]

@nathan-hook, @Classic298

Today I also stumbled upon this topic. I'll give you the context... I created a "Connection" which is my custom web research LangGraph agent:

The connection is configured like so:

I added ENABLE_FORWARD_USER_INFO_HEADERS=True
Got extra HTTP headers but there is missing X-OpenWebUI-Message-Id in the request.

So... is there a bug or inaccurate documentation?

My OWUI is 0.9.6 version:

[Classic298]

I don't think the docs claim that message id is sent to normal openai connections. If it does that needs correction

[nathan-hook]

I don't think the docs claim that message id is sent to normal openai connections. If it does that needs correction

The message id is totally in the current documentation...

https://docs.openwebui.com/reference/env-configuration/#security-variables

Description: Forwards user and session information as HTTP headers to OpenAI API, Ollama API, MCP servers, and Tool servers. If enabled, the following headers are forwarded:
X-OpenWebUI-User-Name
X-OpenWebUI-User-Id
X-OpenWebUI-User-Email
X-OpenWebUI-User-Role
X-OpenWebUI-Chat-Id
X-OpenWebUI-Message-Id

I know I said this in a comment above, but FWIW, it would be amazing if the message id would be sent on all ollama, mcp, openai, and pipeline requests.

[OctoberRust2000]

Agreed! It would be amazing!

[Classic298]

ok the docs is outdated here. the env var was originally documented - and originally - what it had documented was all sent to OpenAI. Later, more items came, which were gated on this env var but not sent to OpenAI. I will edit the docs. Feel free to PR anyways!

[nathan-hook]

Thanks for taking a peek at this discussion and being friendly.

I know that intent is hard to express via written content.

I appreciate all the time and work going into Open WebUI. Keep up the good work.

I will open a PR shortly.