[GH-ISSUE #17167] feat: Support Multiple API Keys per Connection #72796

New Issue

GiteaMirror · 2026-05-13T04:58:19-05:00

GiteaMirror commented

2026-05-13 04:58:19 -05:00

Originally created by @farisemraan on GitHub (Sep 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17167

Check Existing Issues

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

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_

GiteaMirror closed this issue

2026-05-13 04:58:19 -05:00

GiteaMirror commented

2026-05-13 04:58:21 -05:00

@tjbck commented on GitHub (Sep 3, 2025):

You should use Functions for this.

@tjbck commented on GitHub (Sep 3, 2025): You should use Functions for this.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#72796