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

Classy Transactions API

Donations, ticket, and merchandise order transactions.

Classy Transactions API is one of 10 APIs that Classy 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, and an API reference.

This API exposes 5 operations across 3 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.classy.org/2.0.

5 operations 3 paths 3 schemas 3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.classy.org/2.0
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Classy Transactions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth2 clientcredentials access token obtained from POST /oauth2/auth. Passed as Authorization: Bearer {accesstoken}.

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 3 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Transactions 5

Donations, ticket, and merchandise order transactions.

GET
/transactions/{id}
Retrieve a transaction
getTransaction 2 params → 200401404
PUT
/transactions/{id}
Update a transaction
updateTransaction 2 params body → 200401404422
GET
/transactions/{id}/items
List a transaction's line items
listTransactionItems 1 param → 200401
GET
/transactions/{id}/acknowledgements
List a transaction's acknowledgements
listTransactionAcknowledgements 1 param → 200401
POST
/transactions/{id}/acknowledgements
Send an acknowledgement for a transaction
createTransactionAcknowledgement 1 param body → 200401

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Transaction (25 properties), TransactionItem (11 properties), Error (3 properties). Each schema is shown below with its type and property counts.

TransactionItem
object
11 properties
Transaction
object
Field names confirmed against the official "Fetch Multi-Item Order" Postman collection example response.
25 properties
Error
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

classy-org-transactions-api-openapi.yml Raw ↑

Other APIs Classy publishes across the network.

Classy Authentication API
Classy Campaigns API
Classy Designations API
Classy Fundraising Pages API
Classy Fundraising Teams API
Classy Members API
Classy Organizations API
Classy Recurring Donation Plans API
Classy Supporters API
Where this information came from

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