Authenticate with the Classy (now rebranded GoFundMe Pro) API and list an organization's campaigns and transactions
domain: developers.gofundme.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request API access/app credentials (client ID and secret) through the developer portal for your organization
Obtain an OAuth2 access token using the client-credentials grant against the token endpoint
Call the organizations/{id}/campaigns endpoint (or the equivalent campaign list resource) with the bearer token to list active campaigns
Call the organizations/{id}/transactions or campaigns/{id}/transactions endpoint to retrieve donation transactions, using pagination parameters for large result sets
Refresh the OAuth token before expiry using the refresh token or by re-requesting a client-credentials token
Check the deprecation schedule in the developer portal before building against any endpoint, since the platform is mid-rebrand
Known gotchas
Classy has been rebranded to 'GoFundMe Pro' and developer docs have moved from developers.classy.org to developers.gofundme.com/pro — old bookmarked doc URLs may redirect or go stale
Some campaign/progress endpoints are public (no auth) while transaction-level data requires OAuth2 with appropriate scopes — don't assume all endpoints need the same auth
A V2-to-current migration guide exists in the docs; verify you're not building against a deprecated V1/V2 path that's on the removal schedule
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?