github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 14:39:31 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #21605] issue: Incorrect Responses API URL #122845

New Issue
Closed
opened 2026-05-21 01:54:06 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-21 01:54:06 -05:00
Owner
Copy Link

Originally created by @lordneon on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21605

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.8.3

Ollama Version (if applicable)

No response

Operating System

Ubuntu 24.04

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

From the docs, https://docs.openwebui.com/reference/api-endpoints/

The example request:
curl -X POST http://localhost:3000/api/responses -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d '{"model": "gpt-4.1","input": "Explain quantum entanglement in simple terms."}'

This should work as intended and return a response.

Actual Behavior

You get an {"detail":"Method Not Allowed"}

Steps to Reproduce

Deploy latest docker version of open-webui
Grab API key for user account
Following API docs instructions.

Logs & Screenshots

open-webui | 2026-02-19 13:26:44.827 | INFO | uvicorn.protocols.http.httptools_impl:send:483 - :0 - "POST /api/responses HTTP/1.1" 405

Additional Information

Solution is to use http://localhost:3000/openai/responses, but this is contrary to what the docs say. Likely need an routing alias so that api/responses work.

Originally created by @lordneon on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21605 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.3 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 24.04 ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior From the docs, https://docs.openwebui.com/reference/api-endpoints/ The example request: curl -X POST http://localhost:3000/api/responses -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d '{"model": "gpt-4.1","input": "Explain quantum entanglement in simple terms."}' This should work as intended and return a response. ### Actual Behavior You get an `{"detail":"Method Not Allowed"}` ### Steps to Reproduce Deploy latest docker version of open-webui Grab API key for user account Following API docs instructions. ### Logs & Screenshots open-webui | 2026-02-19 13:26:44.827 | INFO | uvicorn.protocols.http.httptools_impl:send:483 - :0 - "POST /api/responses HTTP/1.1" 405 ### Additional Information Solution is to use `http://localhost:3000/openai/responses`, but this is contrary to what the docs say. Likely need an routing alias so that `api/responses` work.
GiteaMirror added the bug label 2026-05-21 01:54:06 -05:00
GiteaMirror commented 2026-05-21 01:54:10 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Feb 19, 2026):

@Classic298 does not exist and should be removed.

<!-- gh-comment-id:3929179983 --> @tjbck commented on GitHub (Feb 19, 2026): @Classic298 does not exist and should be removed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#122845
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?