-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Extend and document API v2 #1175
Comments
I think there is no documentation so far on the API v2 endpoints. However I'm not sure if that would benefit anyone as it seems to me that they more are targeted at internal use of RTD. What would you like to do with the API? I guess for most user facing purposes the API v1 is just fine (like crawling through the details of a specific project etc). |
I was hoping to build a dashboard that would allow me to trigger builds for my sites. Things like scrutinizer, travis CI and rtd. Edit: |
Ok, I don't think it is possible so far to use the API to create a new project. But we are ofcourse happy to accept any patches in that regard. I think triggering a build is already possible using the post-commit-hook described on your project's page: |
If you really want to push this idea further it might be good to open a new ticket for every aspect that you want to add to the API. We are happy to review any individual request. |
The idea here is to have API V2 eventually replace the old V1 API. It's Add it to the massive list of things to do, but it's definitely something On Fri, Jul 10, 2015 at 7:34 AM, Gregor Müllegger [email protected]
Eric Holscher |
I have seen this detailed in the issues here but I can't find any place that details how to use this. I have been trying to get API details through Guzzle but I am not having a lot of luck on how to format URLs (builds for example).
Are there any docs for the v2 API endpoints?
The text was updated successfully, but these errors were encountered: