-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where is the full JSONRPC spec or ServiceDescription.json? #239
Comments
This is the repo for the web site and probably not quite where you wanted to ask this, but I see why you might have decided this was the right place. Generally questions like this are best done on our forums (https://forum.kodi.tv). Our Github stuff is mostly for reporting bugs and problems. Anyway, all the JSON specs are on the wiki at: https://kodi.wiki/view/JSON-RPC_API I'm going to go ahead and close this. |
Thank you for the quick response and the clarification.
Ok, thank you for pointing me into the right direction.
While the wiki might be the right place for developers to see examples and human readable specs, unfortunately the wiki does not contain or link (at least I did not find it) a machine readable spec (e.g. https://datatracker.ietf.org/doc/html/draft-wright-json-schema), that can be used to autogenerate code from it. I'm going to ask in the forum, Edit
|
Hey,
I'm trying to find the http://www.xbmc.org/jsonrpc/ServiceDescription.json to automatically generate client code for my Kodi API client.
Loading my local Kodi instance JSONRPC specs file (http://my-kodi-host:8080/jsonrpc) shows the follwing response (abridged):
The linked id (http://xbmc.org/jsonrpc/ServiceDescription.json) is not available online (I know, it is just an ID, but I would have expected, that it's still downloadable) and unfortunately the local JSONRPC specs file is incomplete. For example there is no mention of "Input.Back" (see https://kodi.wiki/view/JSON-RPC_API/v12#Input.Back).
I hope someone can help me out with that...
My Questions:
Thank you
sandreas
The text was updated successfully, but these errors were encountered: