I have searched the existing issues and discussions.
Problem Description
I have been advised that the OpenAPI standard allows for either a YAML or JSON, and currently Open-WebUI only supports JSON so cannot be used by projects that went down the YAML path.
eg: Obsidian RestAPI.
Can the devs please consider support for openapi.yaml
Desired Solution you'd like
Tools Server functionality to support YAML in addition to JSON, specifically openapi.yaml providing broader compatibility.
Alternatives Considered
No response
Additional Context
No response
Originally created by @smithinoz on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12543
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
I have been advised that the OpenAPI standard allows for either a YAML or JSON, and currently Open-WebUI only supports JSON so cannot be used by projects that went down the YAML path.
eg: Obsidian RestAPI.
Can the devs please consider support for openapi.yaml
### Desired Solution you'd like
Tools Server functionality to support YAML in addition to JSON, specifically openapi.yaml providing broader compatibility.
### 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 @smithinoz on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12543
Check Existing Issues
Problem Description
I have been advised that the OpenAPI standard allows for either a YAML or JSON, and currently Open-WebUI only supports JSON so cannot be used by projects that went down the YAML path.
eg: Obsidian RestAPI.
Can the devs please consider support for openapi.yaml
Desired Solution you'd like
Tools Server functionality to support YAML in addition to JSON, specifically openapi.yaml providing broader compatibility.
Alternatives Considered
No response
Additional Context
No response
@tjbck commented on GitHub (Apr 7, 2025):
Great suggestion, PR welcome!
@spammenotinoz commented on GitHub (Apr 11, 2025):
Thank-you