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

Paddle Transactions API

The Transactions API from Paddle — 3 operation(s) for transactions.

Paddle Transactions API is one of 14 APIs that Paddle 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 4 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 2 base URLs: https://api.paddle.com, https://sandbox-api.paddle.com.

5 operations 3 paths 4 schemas 3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.paddle.com
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — Authenticate with your Paddle API key passed in the Authorization header with the Bearer prefix, e.g. Authorization: Bearer pdlliveapikey....

Paths & Operations 5

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

Transactions 5
GET
/transactions
List transactions
list-transactions 3 params → 200
POST
/transactions
Create a transaction
create-transaction body → 201
GET
/transactions/{transaction_id}
Get a transaction
get-transaction 1 param → 200
PATCH
/transactions/{transaction_id}
Update a transaction
update-transaction 1 param body → 200
GET
/transactions/{transaction_id}/invoice
Get a PDF invoice for a transaction
get-transaction-invoice 1 param → 200

Schemas 4

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

Transaction
object
10 properties
TransactionCollection
object
2 properties
TransactionEntity
object
2 properties
Meta
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paddle-transactions-api-openapi.yml Raw ↑

Other APIs Paddle publishes across the network.

Paddle Addresses API
Paddle Adjustments API
Paddle Businesses API
Paddle Customers API
Paddle Discounts API
Paddle Event Types API
Paddle Events API
Paddle Notification Settings API
Paddle Notifications API
Paddle Prices API
Paddle Products API
Paddle Reports API
Where this information came from

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