GoFundMe Pro API
Agent-ready OpenAPI document · curated by JenticPaymentsBilling Subscriptionsoauth2303 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Run GoFundMe Pro fundraising operations: create campaigns, list transactions, manage recurring donation plans, track supporters, and pull annual summary reports. Built for enterprise nonprofits.
Use for: List all transactions for campaign 12345 from GoFundMe Pro, Cancel a supporter's recurring donation plan, Generate the annual summary report for an organisation, Get the receipt for a specific transaction
Not supported: Does not handle the consumer GoFundMe.com personal-fundraiser product, low-level card processing, or accounting and tax filing - use for GoFundMe Pro (Classy) enterprise nonprofit fundraising only.
Jentic publishes the only available OpenAPI specification for GoFundMe Pro API, keeping it validated and agent-ready. The GoFundMe Pro API (formerly Classy) is the enterprise fundraising platform used by nonprofits to run campaigns, peer-to-peer fundraising, recurring donations, ticketed events, donor matching, and supporter engagement. It exposes 303 endpoints covering campaigns, transactions, recurring donation plans, supporters, dedications, fundraising teams, ecards, designations, comments, branding, appeal sets, and reporting. Authentication is OAuth 2.0 with a documented rate limit of 1800 requests per minute per application.
Install Jentic One Beta
Connect the GoFundMe Pro API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoFundMe Pro API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgofundme.com%2Fgofundme" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgofundme.com%2Fgofundme" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with GoFundMe Pro API.
Pull transactions and transaction items for finance reconciliation, including receipts
Manage recurring donation plans, including pausing or cancelling on behalf of a supporter
Create and update campaign metadata such as appeal sets, dedications, ecards, and FAQs
Track campaign credentials, channels, and feed items used by frontends and embeds
Generate annual summary reports for an organisation or for an individual supporter
Read activity, comments, and matched-transaction records to surface engagement signals
Use Cases
Patterns agents use GoFundMe Pro API for, with concrete tasks.
★ Donor Annual Tax Receipts
Nonprofits generate annual summary reports for supporters at year end. The /organizations/{organization_id}/annual-summary-reports/{year} and /supporters/{supporter_id}/annual-summary endpoints return the consolidated giving totals and downloadable receipts that supporters need for tax filing.
Generate the 2025 annual summary report for organisation 901 and email each supporter their downloadable receipt link.
Recurring Donation Lifecycle Management
Subscriber-care teams handle changes to recurring donations through /campaigns/{campaign_id}/recurring-donation-plans and the /recurring-donation-plans/{recurring_id}/history endpoint. An agent can list active plans, pause one for a supporter who calls in, and read the change history for the audit trail.
Pause supporter 7711's recurring donation on campaign 9001 for 90 days and log the change in the history.
Finance Reconciliation
Finance teams reconcile fundraising income by pulling /transactions/{transaction_id}, /transactions/{transaction_id}/items, and /transactions/{transaction_id}/receipts. These endpoints expose the line-level detail needed to match each donation to a payout and feed the data into accounting software.
Pull all transactions over $1000 for campaign 9001 in May 2026 and produce a CSV with their items and receipts.
AI Agent Donor Engagement
An AI agent uses Jentic to run nonprofit donor stewardship: it lists new transactions, pulls dedications, and drafts personalised thank-you notes that mention the dedication recipient. OAuth credentials stay in your Jentic One instance throughout.
Search Jentic for 'list gofundme pro transactions', load the schema, fetch yesterday's transactions, and draft a thank-you message for each donor referencing any dedication.
Key Endpoints
303 endpoints — jentic publishes the only available openapi specification for gofundme pro api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/transactions/{transaction_id}
Retrieve a transaction
GET
/transactions/{transaction_id}/items
List the items inside a transaction
GET
/transactions/{transaction_id}/receipts
List receipts for a transaction
GET
/campaigns/{campaign_id}/recurring-donation-plans
List recurring donation plans on a campaign
GET
/recurring-donation-plans/{recurring_id}/history
Read the history of a recurring plan
GET
/organizations/{organization_id}/annual-summary-reports/{year}
Generate an annual summary report
GET
/campaigns/{campaign_id}/appeal-set
Read the campaign appeal set
GET
/campaigns/{campaign_id}/activity
Read campaign activity feed
GET
/transactions/{transaction_id}
Retrieve a transaction
GET
/transactions/{transaction_id}/items
List the items inside a transaction
GET
/transactions/{transaction_id}/receipts
List receipts for a transaction
GET
/campaigns/{campaign_id}/recurring-donation-plans
List recurring donation plans on a campaign
GET
/recurring-donation-plans/{recurring_id}/history
Read the history of a recurring plan
GET
/organizations/{organization_id}/annual-summary-reports/{year}
Generate an annual summary report
GET
/campaigns/{campaign_id}/appeal-set
Read the campaign appeal set
GET
/campaigns/{campaign_id}/activity
Read campaign activity feed
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring GoFundMe Pro by hand means running its OAuth 2.0 client-credentials flow against api.classy.org, refreshing access tokens, and navigating the campaign, transaction, and organization report hierarchy yourself. Through Jentic you install once, import GoFundMe Pro from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
GoFundMe Pro puts the resource id in the URL path (/organizations/{organization_id}/... and /campaigns/{campaign_id}/...), so a rule can pin your agent to one organization or campaign: it can read that campaign's transactions, activity, and recurring plans and nothing else. You choose the operations it may call, so it stays read-only unless you add write operations.
Credential isolation
Your GoFundMe Pro client credentials and refresh token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list gofundme pro transactions' or 'get a campaign's annual summary', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without navigating the Classy-era reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Stripe processes the underlying card and ACH transactions referenced by GoFundMe Pro records.
Use Stripe when you need to inspect the actual payment intent, refund, or dispute behind a GoFundMe Pro transaction.
FAQs
Specific to using GoFundMe Pro API through Jentic.
Why is there no official OpenAPI spec for GoFundMe Pro API?
GoFundMe Pro publishes a JSON spec on its developer portal but it is not maintained against the live API and contains drift. Jentic generates and maintains a corrected OpenAPI specification so AI agents and developers can call GoFundMe Pro API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the GoFundMe Pro API use?
GoFundMe Pro uses OAuth 2.0 with both application and member flows (OAuth2Application and OAuth2Member). Tokens are issued from the developer portal. Through Jentic, client credentials and refresh tokens are stored encrypted and rotated automatically.
Can I cancel a recurring donation plan with the GoFundMe Pro API?
Yes. The /recurring-donation-plans endpoints expose the plan lifecycle, and /recurring-donation-plans/{recurring_id}/history returns the change history so you can confirm cancellations took effect for audit purposes.
What are the rate limits for the GoFundMe Pro API?
The default rate limit is 1800 requests per minute per application. Responses include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers, plus a Retry-After value on 429 responses. Internal applications are not subject to rate limits.
How do I generate an annual summary report through Jentic?
Run a Jentic search for 'gofundme pro annual summary', load the schema for GET /organizations/{organization_id}/annual-summary-reports/{year}, and execute it with the organisation ID and year. Install with pip install jentic and chain search, load, and execute.
Does the GoFundMe Pro API support transaction receipts?
Yes. GET /transactions/{transaction_id}/receipts returns the receipt records associated with a transaction so finance and supporter-care teams can resend a receipt or attach it to a tax-summary email.
Can I limit what my agent is allowed to do with the GoFundMe Pro API?
Yes. Because Jentic One is self-hosted, your own rules decide which GoFundMe Pro operations and credentials the agent may use. GoFundMe Pro puts the resource id in the URL path, such as /organizations/{organization_id}/... and /campaigns/{campaign_id}/..., so a rule can pin the agent to a single organization or campaign and let it read only that campaign's transactions, activity, and recurring plans. You choose which operations it may call, so it stays read-only, for example GET /transactions/{transaction_id}, unless you add write operations yourself.
GET STARTED