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_
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 @texasbones11 on GitHub (Jun 5, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14701
Check Existing Issues
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:
Alternatives Considered
No response
Additional Context
No response