How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

GoFundMe Transaction API

Transactions have three types of attributes relating to Passport: raw, charged, and normalized.Raw attributes reflect the donor/purchaser's intent when creating the Transaction. The only attribute directly specified on the Transaction is `raw_currency_code` - the other visible attributes (`raw_total_gross_amount`, `raw_donation_gross_amount`, and `raw_overhead_net_amount`) are all derived from the raw values set on the transaction's items.Charged attributes reflect the values that are actually charged when the payment is processed. Since the potential values for a Transaction's `charged_currency_code` should be limited to those available to an Organization for processing, this value can differ from the Transaction's `raw_currency_code`. The amount that is charged is reflected in `charged_total_gross_amount`, while the fees are expressed in `charged_classy_fees_amount` and `charged_pp_fees_amount` (`charged_fees_amount` attribute is the sum of these two attributes). There is additionally a `charged_at` timestamp that is used for normalization.Normalized attributes reflect a conversion from raw and/or charged attributes into the Transaction's `currency_code`, which is the same for all Passport-enabled entities associated with the Transaction's Organization. This normalization occurs to allow for a constant basis of comparison across each of these entities. These normalized values are all converted from the associated raw or charged attributes, preferring the charged attribute over the raw attribute if available. For example, `charged_total_gross_amount` will be used instead of `raw_total_gross_amount` if both `charged_total_gross_amount` and `charged_currency_code` are present. If `charged_at` is also present, the exchange rate between `charged_currency_code` and `currency_code` at that time will be used if/when the Transaction is renormalized.It should be noted that there is no notion of raw fees, as these are calculated at the time that a Transaction is charged and therefore only reflected as charged attributes. If a transaction is flagged as 'fee-on-top', this will be reflected by an increase in the `charged_total_gross_amount` that will not be visible in `raw_total_gross_amount`.Transactions may be in a number of different states: success, incomplete, canceled, refunded, cb_initiated, cb_lost, test, pending, failedAn additional transaction attribute relating to Passport is the `tax_entity_id`. Tax entities indicate that an Organization is tax compliant within a certain country. A single organization may have more than one tax entity. The `tax_entity_id` listed on the Transaction indicates which of the Organization's tax entities indicates the tax compliance of the Transaction.Transactions may have an associated 'context' attribute which provides data about the Transaction's original Campaign (this does not change between hard credit transfers) and whether or not the transaction is considered to incorporate Passport functionality. This attribute can be used for filtering and/or sorting when using index endpoints.

GoFundMe Transaction API is one of 72 APIs that GoFundMe publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. 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 8 operations across 6 paths, and defines 14 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.

8 operations 6 paths 14 schemas 4 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://pro.gofundme.com/api/2.0
Authentication
OAuth 2.0, OAuth 2.0
Resource Areas
1

Authentication & Security 2

GoFundMe Transaction 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 application
  • OAuth2Member — OAuth bearer token for client application with additional member context

Paths & Operations 8

Across 6 paths, the API surfaces 8 operations — 4 GET, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Transaction 8

Transactions have three types of attributes relating to Passport: raw, charged, and normalized. Raw attributes reflect the donor/purchaser's intent when creating the Transaction.…

GET
/transactions/{transaction}
fetchTransaction
fetchTransaction 2 params → 200403404
PUT
/transactions/{transaction}
updateTransaction
updateTransaction 1 param body → 200403404
GET
/campaigns/{campaign}/transactions
listCampaignTransactions
listCampaignTransactions 5 params → 200403404
POST
/campaigns/{campaign}/transactions
createCampaignTransaction
createCampaignTransaction 1 param body → 200403404
GET
/organizations/{organization}/transactions
listOrganizationTransactions
listOrganizationTransactions 4 params → 200403404
GET
/recurring-donation-plans/{recurring_donation_plan}/transactions
listRecurringDonationPlanTransactions
listRecurringDonationPlanTransactions 3 params → 200403404
POST
/recurring-donation-plans/{id}/transactions/{transaction_id}/reprocess
reprocessRecurringDonationPlanTransaction
reprocessRecurringDonationPlanTransaction 2 params body → 200403404
PUT
/reprocess-attempt-info/{reprocess_attempt_info}
updateReprocessAttemptInfo
updateReprocessAttemptInfo 1 param body → 200403404

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are Transaction (96 properties), CampaignTransactionFillable (32 properties), TransactionFillable (25 properties), PaginatedResponse (13 properties). Each schema is shown below with its type and property counts.

CampaignTransactionFillable
object
32 properties
ReprocessAttemptInfo
object
6 properties
TransactionContext
object
13 properties
PaginatedResponse
object
13 properties
OfflinePaymentInfo
object
4 properties
ForbiddenResponse
object
1 property
ResourceNotFoundResponse
object
1 property
TransactionItemFillable
object
5 properties
Transaction
object
96 properties
ReprocessAttemptInfoFillable
object
5 properties
AnswerFillable
object
1 property
Answer
object
9 properties
PaginationLink
object
Object referencing a page for the resource queried that can be used to fetch that page.
3 properties
TransactionFillable
object
25 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gofundme-transaction-api-openapi.yml Raw ↑

Other APIs GoFundMe publishes across the network.

Classy Login (OpenID Connect SSO)
Classy Pay
GoFundMe Acknowledgement API
GoFundMe Activity API
GoFundMe Annual Summary API
GoFundMe Answer API
GoFundMe API App API
GoFundMe Appeal Set API
GoFundMe Branding API
GoFundMe Brandkit API
GoFundMe Campaign API
GoFundMe Campaign Channel API
Where this information came from

This is an independent, third-party profile of GoFundMe Transaction 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.