mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-10 07:43:10 -05:00
feat: enable API key authentication for Docling integrations #6182
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kaileywong on GitHub (Aug 22, 2025).
Check Existing Issues
Problem Description
Currently, Open WebUI cannot connect to a Docling service that requires API key authentication. This prevents integration with secured Docling instances where authentication is necessary.
Desired Solution you'd like
Introduce a new environment variable, e.g.
DOCLING_API_KEY, that allows users to configure an API key for Docling.When Open WebUI makes requests to Docling service, if
DOCLING_API_KEYis set, include it in the request headers as:X-Api-Key: <DOCLING_API_KEY>If the variable is not set, requests proceed without the header (preserves current behavior)
Alternatives Considered
No response
Additional Context
No response
@palazski commented on GitHub (Oct 2, 2025):
I need this as well. But having the option to change the header name would be much better. Docling itself requires X-Api-Key, but if you were to deploy Docling to a serverless service, they usually require you to pass your API key in the header, which is "Authorization" in general. It may not be Docling's API key, but needed in the header nevertheless in that situation.
I couldn't manage to deploy Docling to a serverless service tho, neither RunPod nor Lightning AI Cloud.
@metabis commented on GitHub (Oct 7, 2025):
same thing here
same endpoint api than ollama ?
I have saw that we need to downgrade docling version to make it works with old API endpoint