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

Spreedly Transactions API

The transactions API from Spreedly — 5 operation(s) for transactions.

Spreedly Transactions API is one of 26 APIs that Spreedly 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 6 operations across 5 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://core.spreedly.com/v1.

6 operations 5 paths 21 schemas 3 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://core.spreedly.com/v1
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Spreedly Transactions API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basic_auth).

  • basic_auth — Unless otherwise noted, all calls to the Spreedly API use [HTTP basic authentication](https://en.wikipedia.org/wiki/Basicaccessauthentication) over HTTPS. Use…

Paths & Operations 6

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

transactions 6
GET
/transactions/{transaction_token}
Show transaction
show-transactions 1 param → 200401404
PATCH
/transactions/{transaction_token}
Update transaction
update-transactions 1 param → 200401404422
POST
/transactions/{transaction_token}/complete
Complete transaction
complete-transactions 1 param → 200401422
GET
/transactions
List transactions
list-transactions 4 params → 200401
POST
/transactions/{transaction_token}/confirm
Confirm transaction
confirm-transactions 1 param body → 200401422
GET
/transactions/{transaction_token}/transcript
Transaction transcript
transcript-transactions 1 param → 200401404

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are payment_method (42 properties), purchase_request (38 properties), protection_parameters (32 properties), protect_fraud_check_response (23 properties). Each schema is shown below with its type and property counts.

purchase_request
object
38 properties
threeds_purchase_response
object
1 property
payment_snapshot
object
When Recover is attempted, provides an overview of the results at the time of the current transaction. For more information on Recover, see [the guide](https:/…
10 properties
transaction_core_parameters
object
16 properties
bank_account
object
7 properties 4 required
recover_params
object
When attempting Recover, the following parameters may be used. For more information on Recover, see [the guide](https://developer.spreedly.com/docs/recover).
3 properties 1 required
purchase
object
1 property
transactions_response
object
1 property
protection_parameters
object
Additional fields that are accepted by the Protection provider, including a testscenario object to indicate valid Protect test flow options. Please refer to ou…
32 properties 3 required
provision_network_token
boolean
true if this transaction should attempt to provision a network token. false or omit this element to not provision a network token for this transaction. Please…
protect_fraud_check_response
object
When a Fraud Check is attempted, provides an overview of the results at the time of the current transaction. For more information on Protection Fraud Checks, s…
23 properties
apple_pay
object
2 properties 1 required
payment_method
object
42 properties
google_pay
object
10 properties 1 required
purchase_response
object
1 property
credit_card
object
Credit card element
22 properties 5 required
network_tokenization
object
The network tokenization details for the transaction
9 properties
gateway_specific_fields
array
The list of gateway specific fields that can be specified in supported gateway transactions
errors
array
purchase_parameters
object
update_transaction_response
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

spreedly-transactions-api-openapi.yml Raw ↑

Other APIs Spreedly publishes across the network.

Spreedly Access Secrets API
Spreedly Authorize API
Spreedly Capture API
Spreedly Card Refresher API
Spreedly Certificates API
Spreedly Claim API
Spreedly Composer API
Spreedly Credit API
Spreedly Environments API
Spreedly Events API
Spreedly Gateways API
Spreedly General Credit API
Where this information came from

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