[GH-ISSUE #14701] feat: Model Alias in API #71943

New Issue

GiteaMirror · 2026-05-13T03:55:08-05:00

GiteaMirror commented

2026-05-13 03:55:08 -05:00

Originally created by @texasbones11 on GitHub (Jun 5, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14701

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

The current implementation of the API does not allow for the use of model aliases when making API calls. Instead, the technical model name must be used, which limits the flexibility of the system.

When a model name is edited in the admin panel, the new name is not recognized by the API as an alias for the underlying technical model name. This means that any scripts or applications using the API must be updated to use the new technical model name, rather than the alias.

Desired Solution you'd like

The goal is to enable the use of model aliases in API calls, allowing for the decoupling of the alias from the underlying technical model name. This would enable the following:

The ability to change the underlying model used by an alias without updating scripts or applications

Alternatives Considered

No response

Additional Context

No response

Originally created by @texasbones11 on GitHub (Jun 5, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14701 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description The current implementation of the API does not allow for the use of model aliases when making API calls. Instead, the technical model name must be used, which limits the flexibility of the system. When a model name is edited in the admin panel, the new name is not recognized by the API as an alias for the underlying technical model name. This means that any scripts or applications using the API must be updated to use the new technical model name, rather than the alias. ### Desired Solution you'd like The goal is to enable the use of model aliases in API calls, allowing for the decoupling of the alias from the underlying technical model name. This would enable the following: - The ability to change the underlying model used by an alias without updating scripts or applications ### Alternatives Considered _No response_ ### Additional Context _No response_

GiteaMirror closed this issue

2026-05-13 03:55:09 -05:00

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#71943