Blogger vs Open Collective

Blogger API v3 is Google's REST/JSON interface for its blogging platform, letting apps retrieve and manage blogs, posts, comments, and pages. Public data can be read with a plain API key, but writing content or touching private data requires a full OAuth 2.0 authorization flow. The docs still list the deprecated v1.0 and v2.0 protocol guides alongside the current v3.0 reference, reflecting a mature, low-churn API that hasn't needed a v4.

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.