Social — entry 022 of 38
Open Collective
Open Collective's GraphQL API (v2) queries collectives, expenses, transactions, and members for the platform's transparent nonprofit/open-source funding model, and public collective data is readable with no authentication at all. Its own docs flag the older REST API as still running but no longer developed, pointing new integrations at the GraphQL surface and a companion PDF service (for receipts and invoices) that accepts either a personal token or an OAuth bearer token. A personal access token, not a full OAuth app-review flow, is the documented way to authenticate for private or write access.
GreatAPIs Score
Embed this badge
<a href="https://greatapis.com/api/open-collective/"><img src="https://greatapis.com/badge/open-collective.svg" alt="Scored 78 on greatapis.com"></a>Auth quickstart
- Get a key at the provider
- Send it on every request as a header
Authorization: <key> - The exact header isn't documented — Authorization is a common default; confirm in the provider's docs.
Your key is stored only in this browser (localStorage) and sent directly to the API — never to greatapis.
Developer reference
10 requests per minute for unauthenticated GraphQL v2 calls