GoFundMe Fundraising Team Transfer API
Transfer a Fundraising Team within its Campaign/subteam infrastructure. This is done by specifying the team's direct parent, making it either a direct team for its Campaign or a subteam for another team for its Campaign.The endpoint requires two parameters within its post body: `new_parent_id` and `new_parent_type`. These parameters are used to specify the new direct parent of the Fundraising Team. At the moment, this can either be the Fundraising Team's Campaign itself (making it a direct team for the Campaign) or another Fundraising Team associated with the Fundraising Team's Campaign (making it a subteam of the specified team).NOTE: An error will be returned if the new parent for a Fundraising Team is currently a subteam of the Fundraising Team.
GoFundMe Fundraising Team Transfer API is one of 72 APIs that GoFundMe publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Fundraising Team Transfer. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.
This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.
Requests are made against a single base URL, https://pro.gofundme.com/api/2.0.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
GoFundMe Fundraising Team Transfer API declares
2 security schemes
for authenticating requests.
It supports OAuth 2.0 (OAuth2Application) using the clientCredentials flow, exposing 2 scopes.
It supports OAuth 2.0 (OAuth2Member) using the password flow, exposing 2 scopes.
By default, every request must be authenticated.
OAuth2Application— OAuth bearer token for client applicationOAuth2Member— OAuth bearer token for client application with additional member context
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
Transfer a Fundraising Team within its Campaign/subteam infrastructure. This is done by specifying the team's direct parent, making it either a direct team for its Campaign or a s…
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Campaign (108 properties), FundraisingTeam (28 properties), ForbiddenResponse (1 property), ResourceNotFoundResponse (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from GoFundMe 12
Other APIs GoFundMe publishes across the network.
This is an independent, third-party profile of GoFundMe Fundraising Team Transfer API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.