Discord vs Open Collective

Discord's REST and Gateway APIs let bots and apps manage servers, channels, messages, and slash commands, authenticated with a bot token for server-side integrations or OAuth2 for user-facing flows like account linking. Rate limits are enforced per route and per bucket, and most guild-management scopes only work once the bot has been added to a server with matching OAuth2 permission scopes.

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.