Paddle Billing

Read and write Paddle Billing customers, addresses, businesses, products, prices and discounts, update subscriptions, and read transactions, adjustments, credit balances and events.

Keep Paddle customers, catalogue and subscriptions aligned with CRM, product and finance systems, and feed transactions into accounting.

Build a flow with Paddle Billing Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

addresses

Create address
Destination
Not retried automatically
Approval before production
Creates a address in Paddle Billing.
addresses.create
Get address
Source
One address by Paddle ID.
addresses.get
List addresses of a customer
Source
Addresses of a customer with cursor pagination (after).
addresses.list
Update address
Destination
Provider duplicate protection
Approval before production
Updates supplied address fields. Archiving is not automated.
addresses.update

adjustments

List adjustments (credits and refunds, read only)
Source
Adjustments (credits and refunds, read only) with cursor pagination (after).
adjustments.list

businesses

Create business
Destination
Not retried automatically
Approval before production
Creates a business in Paddle Billing.
businesses.create
Get business
Source
One business by Paddle ID.
businesses.get
List businesses of a customer
Source
Businesses of a customer with cursor pagination (after).
businesses.list
Update business
Destination
Provider duplicate protection
Approval before production
Updates supplied business fields. Archiving is not automated.
businesses.update

credit balances

List credit balances of a customer
Source
Credit balances of a customer with cursor pagination (after).
credit_balances.list

customers

Create customer
Destination
Not retried automatically
Approval before production
Creates a customer in Paddle Billing.
customers.create
Get customer
Source
One customer by Paddle ID.
customers.get
List customers
Source
Customers with cursor pagination (after).
customers.list
Update customer
Destination
Provider duplicate protection
Approval before production
Updates supplied customer fields. Archiving is not automated.
customers.update

discounts

Create discount
Destination
Not retried automatically
Approval before production
Creates a discount in Paddle Billing.
discounts.create
Get discount
Source
One discount by Paddle ID.
discounts.get
List discounts
Source
Discounts with cursor pagination (after).
discounts.list
Update discount
Destination
Provider duplicate protection
Approval before production
Updates supplied discount fields. Archiving is not automated.
discounts.update

events

List events
Source
Events with cursor pagination (after).
events.list

prices

Create price
Destination
Not retried automatically
Approval before production
Creates a price in Paddle Billing.
prices.create
Get price
Source
One price by Paddle ID.
prices.get
List prices
Source
Prices with cursor pagination (after).
prices.list
Update price
Destination
Provider duplicate protection
Approval before production
Updates supplied price fields. Archiving is not automated.
prices.update

products

Create product
Destination
Not retried automatically
Approval before production
Creates a product in Paddle Billing.
products.create
Get product
Source
One product by Paddle ID.
products.get
List products
Source
Products with cursor pagination (after).
products.list
Update product
Destination
Provider duplicate protection
Approval before production
Updates supplied product fields. Archiving is not automated.
products.update

subscriptions

Get subscription
Source
One subscription by Paddle ID.
subscriptions.get
List subscriptions
Source
Subscriptions with cursor pagination (after).
subscriptions.list
Update subscription
Destination
Provider duplicate protection
Approval before production
Updates subscription items, address, business, collection mode, discount and custom data. Changes bill on the next billing period or not at all.
subscriptions.update

transactions

Get transaction
Source
One transaction by Paddle ID.
transactions.get
List transactions (invoices and payments, read only)
Source
Incremental
Transactions (invoices and payments, read only) with cursor pagination (after) and incremental updated_at[GT].
transactions.list

Authentication

Paddle API key (Bearer)

Plans and access

All Paddle Billing accounts include API access. Paddle Classic is a different API and is not covered. API keys carry per-entity permissions (for example customer.write, subscription.read).

Test environment

Paddle provides a separate sandbox account at sandbox-api.paddle.com with its own API keys.

Rate limits

Paddle limits requests per IP and returns HTTP 429 with Retry-After; Nexra backs off.

Pagination

per_page (max 200, transactions 30, adjustments 50) with meta.pagination.next and has_more.

Provider events

Paddle notification destinations deliver events such as subscription.updated and transaction.completed. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Paddle Billing creates subscriptions from completed checkouts and transactions; subscription create is not available through the API and is not offered.
Subscription update only allows proration modes that bill on the next billing period or not at all (prorated_next_billing_period, full_next_billing_period, do_not_bill); immediate billing, next_billed_at changes and scheduled-change removal are not automated.
Transactions (Paddle's invoices) and adjustments (credits and refunds) are read only; creating or revising transactions, one-time charges, refunds, credits, cancellations, pauses and resumes are not automated.
Archiving (status changes) of customers, addresses, businesses, products, prices and discounts is not automated.
Only transactions support an updated_at filter; other lists are full reads ordered by ID.
Paddle has no usage or metered record API.
Paddle does not document an idempotency key; uncertain creates are not repeated automatically.

Developer reference

Create the Paddle credentials described above with the narrowest permissions your flows need.
In Nexra, open Connect, then Connections, then New connection, choose Paddle Billing, enter its settings and credentials, and tick only the write actions you need. Connection guide
Test the connection, then use its actions as flow sources and destinations. Flow guide

Paddle docsAPI reference Paddle docsAuthentication Paddle docsRate limits Paddle docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/paddle and the Connections API.