Paddle API
- Paddle API v1
Vendor coverage
Paddle API changes & breaking changes
Paddle Billing sits directly in the revenue path for SaaS products. Detektu diffs Paddle's official OpenAPI contract so a changed subscription or transaction schema becomes a finding before it becomes a failed checkout or billing incident.
Last checked Oct 20, 2026, 3:46 PM
Detected changes
Latest Paddle API changes
Every entry is a change Detektu detected in Paddle's published contracts, with exact before/after evidence on its page.
No changes on record yet.
Coverage
What Detektu monitors
Official products and contracts checked for changes.
Change model
How Paddle ships changes
The release patterns that shape your integration risk.
Paddle publishes one OpenAPI 3.1 contract for its v1 API, covering the catalog, customers, subscriptions, transactions, notifications, reports, and related billing resources. The stable API surface evolves continuously as Paddle adds billing capabilities and extends existing entities.
Detektu reports each revision with the exact operation and property that changed, so additions remain useful signal while a tightened request or changed response on the billing paths your application calls is easy to identify and review.
From change to finding
Findings you'd see
Illustrative examples. Every real finding carries exact before/after evidence, severity, and source provenance.
Subscription update field becomes required
openapi:PATCH /subscriptions/{subscription_id} ::itemsNew transaction response field published
openapi:GET /transactions/{transaction_id} ::response.200.dataMonitored for you
Do Paddle's changes affect your integration?
Choose the operations and fields your services use. Detektu matches Paddle findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.