Need help with opencollective-api?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

235 Stars 176 Forks MIT License 13.9K Commits 29 Opened issues


Open Collective's API. A GraphQL API powered by Sequelize and PostgreSQL.

Services available


Need anything else?

Contributors list

Open Collective API

Dependency Status CI E2E


If you see a step below that could be improved (or is outdated), please update the instructions. We rarely go through this process ourselves, so your fresh pair of eyes and your recent experience with it, makes you the best candidate to improve them for other users. Thank you!



  1. Make sure you have Node.js version >= 10.
  • We recommend using nvm:
    nvm use
  1. Make sure you have a PostgreSQL database available
  • Check the version: 11.0, 10.3, 9.6.8, 9.5.12, 9.4.17, 9.3.22 or newer
  • Check that the PostGIS extension is available
  • More info in our PostgreSQL Database documentation
  1. For node-gyp, make sure you have Python 2 available and configured as the active version.
  • You can use pyenv to manage Python versions.


We recommend cloning the repository in a folder dedicated to

git clone [email protected]:opencollective/opencollective-api.git opencollective/api
cd opencollective/api
npm install


npm run dev
  • API is started on http://localhost:3060
  • A local email inbox is started on http://localhost:1080


  • If you're running into
    issues related to Python 3 vs Python 2, you can run:
    npm rebuild
  • If you have issues with PostgreSQL, check our dedicated documentation


Summary: This project is currently deployed to staging and production with Heroku. To deploy, you need to be a core member of the Open Collective team.

See: docs/

More documentation:


If you have any questions, ping us on Slack ( or on Twitter (@opencollect).



We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.