Repository navigation
Replies: 1 comment
|
I would absolutely love to do that, but it won't help because OpenAPI specs are not for describing soap endpoints. So it would not be possible to have swagger send the correct requests, and then there is cors which will prevent calling Sonos from any browser source. There is however a project of mine that runs a true rest api in a docker container that has all these endpoints and an OpenAPI specs file and a testing tool like swagger which is called scalar (which looks better in my opinion). This is all generated based on the docs above. I even started a blazor (c# web assembly) front-end but that is more of a work in progress. Check it out at https://github.com/svrooij/sonos-net/tree/feature/net8 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi @svrooij,
First of all, thanks for this great documentation project!
I was wondering if there are any plans to provide a Swagger (OpenAPI) specification file (e.g.,
swagger.jsonoropenapi.yaml)?Having an OpenAPI spec would be extremely beneficial for:
Is this something you would consider adding?
Thanks!
All reactions