You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You obviously coded this software to work with the api's specifications. However I'm more interested in your documentation itself. Like what are the API endpoint URLs? What request type does it use(get or post)? Are the parameters for the requests sent in the request body, or in the URL string after the question mark? I assume you had to reverse engineer it to document it before you could implement it as you've done. Could you please post your actual documentation here?
The text was updated successfully, but these errors were encountered:
Hi @Videogamer555, thanks for opening this issue. Producing documentation for the API has been on my roadmap for quite a while now, however I haven't managed to get around to it just yet. YouTube's InnerTube API changes often, so keeping up with it can be quite a challenge. At least for now, the code base is the best thing I can provide in terms of documentation, which I appreciate is not ideal. As this library is designed for low-level interactions with the InnerTube API, it provides a mechanism for communicating with the API, and knowing which endpoints to hit, which data to provide etc. is currently left as an exercise for the user.
You obviously coded this software to work with the api's specifications. However I'm more interested in your documentation itself. Like what are the API endpoint URLs? What request type does it use(get or post)? Are the parameters for the requests sent in the request body, or in the URL string after the question mark? I assume you had to reverse engineer it to document it before you could implement it as you've done. Could you please post your actual documentation here?
The text was updated successfully, but these errors were encountered: