GoFundMe Transaction Item API
Transaction Items describe the specific donations, tickets, registrations (and more) that could make up a Transaction. Some transactions will only have a single Transaction Item, but others may have many.Like transactions, transaction items have three types of attributes relating to Passport: raw, charged, and normalized.Raw attributes (e.g. `raw_currency_code`, `raw_final_price`, etc.) reflect donor intent through their donation or product purchases. `raw_final_price` represents the total raw value of a transaction item - it is either set directly (as with a direct donation) or derived from the product of `raw_price` (the price of the transaction item's associated product) and the specified quantity. Transaction items associated with a product may also have `raw_overhead_amount` set, which indicates the amount of the `raw_final_price` that is attributed to campaign overhead. All raw amounts are presented in terms of `raw_currency_code`, which is inherited from the transaction item's transaction and cannot be set on a per-item basis.Charged (e.g. `charged_final_price`, `charged_fees_amount`, etc.) attributes are all derived from the transaction item's associated transaction and reflect the percentage that the transaction item contributed to the transaction's raw gross amount. For example, a transaction item that contributed 85% of its transaction's `raw_total_gross_amount` through its `raw_final_price` will see its charged attributes reflect 85% of the transaction's charged attribute values. All of these values will be reflected in terms of the `charged_currency_code` of the transaction item's transaction.Normalized attributes (e.g. `final_price`, `fees_amount`, etc.) reflect a conversion from raw and/or charged attributes into the transaction item's `currency_code`, which is the same for all Passport-enabled entities associated with the transaction item'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_final_price` will be used instead of `raw_final_price` if both `charged_final_price` 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 item is renormalized.
GoFundMe Transaction Item 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 Item. 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 2 operations across 2 paths, and defines 6 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 Transaction Item 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 2
Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.
Transaction Items describe the specific donations, tickets, registrations (and more) that could make up a Transaction. Some transactions will only have a single Transaction Item,…
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are PaginatedResponse (13 properties), TransactionItemFillable (5 properties), PaginationLink (3 properties), 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 Transaction Item 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.