Originally created by @rkuemon on GitHub (Mar 17, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
I want to build a service that automatically creates and starts a new chat in OpenWebUI through the API. Currently, the /api/v1/chats endpoint allows initializing messages within a new chat, but it doesn't actually trigger the chat to start. From what I've seen, you have to send an additional request to /api/chat/completion, but that endpoint requires a "session_id" and another "id," which I've only found accessible via WebSockets. Unfortunately, accessing these would require me to log in using my username and password for the auth token, defeating the whole purpose of using the API.
Desired Solution you'd like
I'd like an option in the /api/v1/chats/new endpoint to automatically start a chat in one step via the API. If anyone knows of an alternative way for me to achieve my goal, I'd appreciate it a lot. :)
Alternatives Considered
No response
Additional Context
No response
Originally created by @rkuemon on GitHub (Mar 17, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
I want to build a service that automatically creates and starts a new chat in OpenWebUI through the API. Currently, the `/api/v1/chats` endpoint allows initializing messages within a new chat, but it doesn't actually trigger the chat to start. From what I've seen, you have to send an additional request to `/api/chat/completion`, but that endpoint requires a "session_id" and another "id," which I've only found accessible via WebSockets. Unfortunately, accessing these would require me to log in using my username and password for the auth token, defeating the whole purpose of using the API.
### Desired Solution you'd like
I'd like an option in the `/api/v1/chats/new` endpoint to automatically start a chat in one step via the API. If anyone knows of an alternative way for me to achieve my goal, I'd appreciate it a lot. :)
### 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 @rkuemon on GitHub (Mar 17, 2025).
Check Existing Issues
Problem Description
I want to build a service that automatically creates and starts a new chat in OpenWebUI through the API. Currently, the
/api/v1/chatsendpoint allows initializing messages within a new chat, but it doesn't actually trigger the chat to start. From what I've seen, you have to send an additional request to/api/chat/completion, but that endpoint requires a "session_id" and another "id," which I've only found accessible via WebSockets. Unfortunately, accessing these would require me to log in using my username and password for the auth token, defeating the whole purpose of using the API.Desired Solution you'd like
I'd like an option in the
/api/v1/chats/newendpoint to automatically start a chat in one step via the API. If anyone knows of an alternative way for me to achieve my goal, I'd appreciate it a lot. :)Alternatives Considered
No response
Additional Context
No response