Is your feature request related to a problem? Please describe.
Straight text ingestion is fast. In most of my cases I am trying to ingest certain policy pages or confluence pages. Confluence has an api which allows me to get html of a page. I can then easily parse and send this as plain text. Currently I am sending a few hundred confluence pages in a couple minutes.
Describe the solution you'd like
It would be nice to have a restapi endpoint to ingest straight text. It should include a document title name, and the text body. Ideally the title could also be a URL to a website location.
Describe alternatives you've considered
Trying to save the documents as text files first. And then ingesting. But the extra overhead here is a lot.
Additional context
While I need a text ingestion api, might be nice to be able to have a file ingestion api as well.
Originally created by @icsy7867 on GitHub (Mar 18, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/1200
Originally assigned to: @tjbck on GitHub.
**Is your feature request related to a problem? Please describe.**
Straight text ingestion is fast. In most of my cases I am trying to ingest certain policy pages or confluence pages. Confluence has an api which allows me to get html of a page. I can then easily parse and send this as plain text. Currently I am sending a few hundred confluence pages in a couple minutes.
**Describe the solution you'd like**
It would be nice to have a restapi endpoint to ingest straight text. It should include a document title name, and the text body. Ideally the title could also be a URL to a website location.
**Describe alternatives you've considered**
Trying to save the documents as text files first. And then ingesting. But the extra overhead here is a lot.
**Additional context**
While I need a text ingestion api, might be nice to be able to have a file ingestion api as well.
Added to our dev branch! You can check out the RAG API endpoints here:http://[Your Open WebUI]/rag/api/v1/docs. Keep us updated and let us know if the current implementation fits into your use-case, if not feel free to elaborate more on your workflow so we can better accommodate, thanks!
<!-- gh-comment-id:2016724113 -->
@tjbck commented on GitHub (Mar 24, 2024):
Added to our dev branch! You can check out the RAG API endpoints here:`http://[Your Open WebUI]/rag/api/v1/docs`. Keep us updated and let us know if the current implementation fits into your use-case, if not feel free to elaborate more on your workflow so we can better accommodate, thanks!
@tjbck I can't find the RAG API endpoint through http://[Your Open WebUI]/rag/api/v1/docs
it show me 404: Not Found
the log from the open web ui pod:
INFO: 10.77.0.2:0 - "GET /rag/api/v1/docs HTTP/1.1" 304 Not Modified
INFO: connection closed
INFO: 10.77.0.2:0 - "GET /favicon/favicon.svg HTTP/1.1" 304 Not Modified
INFO: 10.77.0.2:0 - "GET /_app/version.json HTTP/1.1" 200 OK
INFO: 10.77.0.2:0 - "GET /api/config HTTP/1.1" 200 OK
<!-- gh-comment-id:2696045947 -->
@longfei-zhang commented on GitHub (Mar 4, 2025):
@tjbck I can't find the RAG API endpoint through http://[Your Open WebUI]/rag/api/v1/docs
it show me 404: Not Found
the log from the open web ui pod:
```
INFO: 10.77.0.2:0 - "GET /rag/api/v1/docs HTTP/1.1" 304 Not Modified
INFO: connection closed
INFO: 10.77.0.2:0 - "GET /favicon/favicon.svg HTTP/1.1" 304 Not Modified
INFO: 10.77.0.2:0 - "GET /_app/version.json HTTP/1.1" 200 OK
INFO: 10.77.0.2:0 - "GET /api/config HTTP/1.1" 200 OK
```
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 @icsy7867 on GitHub (Mar 18, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/1200
Originally assigned to: @tjbck on GitHub.
Is your feature request related to a problem? Please describe.
Straight text ingestion is fast. In most of my cases I am trying to ingest certain policy pages or confluence pages. Confluence has an api which allows me to get html of a page. I can then easily parse and send this as plain text. Currently I am sending a few hundred confluence pages in a couple minutes.
Describe the solution you'd like
It would be nice to have a restapi endpoint to ingest straight text. It should include a document title name, and the text body. Ideally the title could also be a URL to a website location.
Describe alternatives you've considered
Trying to save the documents as text files first. And then ingesting. But the extra overhead here is a lot.
Additional context
While I need a text ingestion api, might be nice to be able to have a file ingestion api as well.
@tjbck commented on GitHub (Mar 24, 2024):
Added to our dev branch! You can check out the RAG API endpoints here:
http://[Your Open WebUI]/rag/api/v1/docs. Keep us updated and let us know if the current implementation fits into your use-case, if not feel free to elaborate more on your workflow so we can better accommodate, thanks!@longfei-zhang commented on GitHub (Mar 4, 2025):
@tjbck I can't find the RAG API endpoint through http://[Your Open WebUI]/rag/api/v1/docs
it show me 404: Not Found
the log from the open web ui pod: