[GH-ISSUE #5452] feat: support for passing non-standard sampling parameters (e.g. top_k) in OpenAI-like APIs #133713

New Issue

2026-05-24T23:04:50-05:00

GiteaMirror commented

2026-05-24 23:04:50 -05:00

Originally created by @esceptico on GitHub (Sep 16, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/5452

Is your feature request related to a problem? Please describe.
I’m currently using a custom OpenAI-like API along with open-webui. Everything works great, but there’s a limitation in the current support for the OpenAI-like API. Specifically, there’s no ability to pass non-standard sampling parameters (those not typically supported by the OpenAI interface) such as top_k. As I understand, this limitation is intentional.

Describe the solution you'd like
I would like to have the option to pass all sampling parameters (including non-standard ones) through the OpenAI-like API, similar to how they’re available in the UI. This would allow greater flexibility when interacting with custom APIs.

Describe alternatives you've considered
Currently, the only alternative is to use the parameters that are supported by the standard OpenAI API interface and hardcode the rest. However, this limits functionality for testing purposes :(

Additional context
None

Originally created by @esceptico on GitHub (Sep 16, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/5452 **Is your feature request related to a problem? Please describe.** I’m currently using a custom OpenAI-like API along with open-webui. Everything works great, but there’s a limitation in the current support for the OpenAI-like API. Specifically, there’s no ability to pass non-standard sampling parameters (those not typically supported by the OpenAI interface) such as top_k. As I understand, this limitation is intentional. **Describe the solution you'd like** I would like to have the option to pass all sampling parameters (including non-standard ones) through the OpenAI-like API, similar to how they’re available in the UI. This would allow greater flexibility when interacting with custom APIs. **Describe alternatives you've considered** Currently, the only alternative is to use the parameters that are supported by the standard OpenAI API interface and hardcode the rest. However, this limits functionality for testing purposes :( **Additional context** None

GiteaMirror closed this issue

2026-05-24 23:04:51 -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#133713