I have searched the existing issues and discussions.
Problem Description
I would like to request a feature that allows support for multiple API keys within the same connection.
Use Case:
Currently, a single API key is tied to a connection, which can become restrictive in scenarios such as:
Using providers like Groq, which offer generous daily quotas per API key across different models.
Assigning specific API keys to different users or groups of users.
Proposed Feature:
Extend the connection configuration to accept multiple API keys.
Provide a mechanism to assign keys:
Per user (each user can authenticate with their own key).
Per group (teams share one key).
Load-balanced / quota-aware (rotate keys automatically if one reaches its limit).
Benefits:
More efficient use of provider quotas.
Fairer distribution of resources among users.
Improves flexibility and scalability in multi-user environments.
Example Scenario:
I connect to Groq with several API keys. User A uses their own key, User B shares the team’s key, and the system can automatically switch keys if a quota limit is reached.
Originally created by @farisemraan on GitHub (Sep 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17167
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
I would like to request a feature that allows support for multiple API keys within the same connection.
### Use Case:
Currently, a single API key is tied to a connection, which can become restrictive in scenarios such as:
- Using providers like Groq, which offer generous daily quotas per API key across different models.
- Assigning specific API keys to different users or groups of users.
### Proposed Feature:
- Extend the connection configuration to accept multiple API keys.
- Provide a mechanism to assign keys:
- Per user (each user can authenticate with their own key).
- Per group (teams share one key).
- Load-balanced / quota-aware (rotate keys automatically if one reaches its limit).
### Benefits:
- More efficient use of provider quotas.
- Fairer distribution of resources among users.
- Improves flexibility and scalability in multi-user environments.
### Example Scenario:
I connect to Groq with several API keys. User A uses their own key, User B shares the team’s key, and the system can automatically switch keys if a quota limit is reached.
### Desired Solution you'd like
Something very similar has been done here:
https://github.com/open-webui/open-webui/pull/14046
### Alternatives Considered
_No response_
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @farisemraan on GitHub (Sep 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17167
Check Existing Issues
Problem Description
I would like to request a feature that allows support for multiple API keys within the same connection.
Use Case:
Currently, a single API key is tied to a connection, which can become restrictive in scenarios such as:
Proposed Feature:
Benefits:
Example Scenario:
I connect to Groq with several API keys. User A uses their own key, User B shares the team’s key, and the system can automatically switch keys if a quota limit is reached.
Desired Solution you'd like
Something very similar has been done here:
https://github.com/open-webui/open-webui/pull/14046
Alternatives Considered
No response
Additional Context
No response
@tjbck commented on GitHub (Sep 3, 2025):
You should use Functions for this.