Use API to initiate watching a project


When I run the API GET Projects, only already watched projects are shown. No capability exists to add a GitHub repo to the list of projects; it can only be done manually.

I need this because I am creating a tutorial about continuous integration for Meteor developers. It has a lot of automation, not only to make the tutorial cover a lot of ground quickly, but also to facilitate testing and validating the tutorial while creating it and for future regression testing (I want to know if someone’s changes will break it).

May be there aren’t a lot of other use cases, but lack of this feature puts a hole in an an otherwise 100% automated tutorial. :sob:


:+1: I don’t think it does currently, but I think a good place to add this would be the endpoint. I don’t think it would be hard to have it add a new project if you ask it to kickoff a new build on an unwatched repo, I may be wrong.


You should be able to create a new project on Circle with the following api call.

curl -X POST ''

Create a command line tool to interact with CircleCI REST API

That’s great!

It does just what I wanted now.

Please have a look at the tutorial I mentioned in the post that opened this thread. It contains a lot of ideas and valuable bash snippets for anyone wanting to automate their interactions with GitHub and CircleCI.

Tutorial slide shows - GitHub :: Meteor / CircleCI Continuous Integration Tutorial
Tutorial video play list - YouTube :: Meteor / CircleCI Continuous Integration Tutorial

I introduce CircleCI in Part #6 - Cloud Continuous Integration Please step through to get an idea of what I am trying to achieve.

I’m giving it away for free, (as a professional portfolio piece), so I’d be really grateful if one of you would blog about it or something.

Thanks, and thanks again for getting that working.

Sincere regards,



Is there any special reason for that API call just work with token and not with basic authentication?



Personally, I do not like to use UID/PWD authentication in API calls. APIs are for scripting and managing passwords in scripts is problematic.

So I suspect CircleCI’s reasoning is that tokens are more secure and easier to use so why support UID/PWD as well?


I had the same question and this solution worked well for me, however it would be really nice to include this in the API docs ( so I didn’t have to come searching here for it. Would have saved me some time. Thanks!


is it possible to delete “follow of project” by REST API too?


Can you document this? Took me some time to arrive here.


This will be added to the docs within 48 hours: