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

Upgrade Transactions API

Transactions API (Direct Settle disbursement)

Upgrade Transactions API is one of 3 APIs that Upgrade 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 and API documentation.

This API exposes 5 operations across 5 paths, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version v1.

Requests are made against 2 base URLs: https://partner.upgrade.com/api/checkout, https://partner.credify.tech/api/checkout.

5 operations 5 paths 2 schemas 1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v1
Base URL
https://partner.upgrade.com/api/flexpay
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Upgrade Transactions API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (flexPayOAuth) using the clientCredentials flow. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • flexPayOAuth — OAuth 2.0 client-credentials grant. Client IDs and secrets are issued per merchant and per environment by the Flex Pay integration team (server IP allowlisting…
  • bearerAuth — Access token from the Flex Pay authorization server, included in the Authorization HTTP header for all API requests.

Paths & Operations 5

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

Transactions 5

Transactions API (Direct Settle disbursement)

POST
/v1/transactions
Authorize Transaction
authorizeTransaction 1 param body → 200
GET
/v1/transactions/{transactionId}
Get Transaction
getTransaction 1 param → 200
POST
/v1/transactions/{transactionId}/void
Void Transaction
voidTransaction 2 params body → 200
POST
/v1/transactions/{transactionId}/capture
Capture Transaction
captureTransaction 2 params body → 200
POST
/v1/transactions/{transactionId}/refund
Refund Transaction
refundTransaction 2 params body → 200

Schemas 2

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

TransactionAmountRequest
object
3 properties
Transaction
object
The Transaction object returned by the Transactions API (documented subset).
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

upgrade-transactions-api-openapi.yml Raw ↑

Other APIs Upgrade publishes across the network.

Upgrade Marketing Offers API
Upgrade Orders API
Where this information came from

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