Paddle Billing
Keep Paddle Billing in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
36 ways to read, 15 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Paddle Billing, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create address
addresses.createApproval by rule - Create business
businesses.createApproval by rule - List credit balances of a customer
credit_balances.listRead
Example flow
- Paddle Billing · List credit balances of a customer
credit_balances.listDone - Paddle Billing · Create address
addresses.createMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Paddle Billing.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Paddle Billing
- Paddle Billing's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Paddle test account before you go live.
For developers
Technical detail
Paddle Billing customers, addresses, businesses, catalogue, discounts, subscriptions, draft transactions, adjustments, notifications, reports and metrics.
Paddle API docs- Source actions
- 36
- Destination actions
- 15
- Data types
- 24
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
addresses4
- Create addressDestinationNot retried automaticallyApproval before production
Creates a address in Paddle Billing.
- Get addressSource
One address by Paddle ID.
- List addresses of a customerSource
Addresses of a customer with cursor pagination (after).
- Update addressDestinationProvider duplicate protectionApproval before production
Updates supplied address fields. Archiving is not automated.
adjustments1
- List adjustments (credits and refunds, read only)Source
Adjustments (credits and refunds, read only) with cursor pagination (after).
businesses4
- Create businessDestinationNot retried automaticallyApproval before production
Creates a business in Paddle Billing.
- Get businessSource
One business by Paddle ID.
- List businesses of a customerSource
Businesses of a customer with cursor pagination (after).
- Update businessDestinationProvider duplicate protectionApproval before production
Updates supplied business fields. Archiving is not automated.
credit balances1
- List credit balances of a customerSource
Credit balances of a customer with cursor pagination (after).
credit notes1
- Get adjustment credit note PDFSource
A temporary link to the PDF credit note for an approved adjustment.
customers4
- Create customerDestinationNot retried automaticallyApproval before production
Creates a customer in Paddle Billing.
- Get customerSource
One customer by Paddle ID.
- List customersSource
Customers with cursor pagination (after).
- Update customerDestinationProvider duplicate protectionApproval before production
Updates supplied customer fields. Archiving is not automated.
discount groups2
- Get discount groupSource
One discount group by Paddle ID.
- List discount groupsSource
Discount groups with cursor pagination (after).
discounts4
- Create discountDestinationNot retried automaticallyApproval before production
Creates a discount in Paddle Billing.
- Get discountSource
One discount by Paddle ID.
- List discountsSource
Discounts with cursor pagination (after).
- Update discountDestinationProvider duplicate protectionApproval before production
Updates supplied discount fields. Archiving is not automated.
event types1
- List event typesSource
Every webhook event type Paddle can send, with its group and API versions.
events1
- List eventsSource
Events with cursor pagination (after).
metrics1
- Get metricsSource
Daily timeseries for a dashboard metric (MRR, MRR change, active subscribers, revenue, refunds, chargebacks or checkout conversion) over a date range.
notification logs1
- List notification delivery logsSource
Delivery attempts for one notification, with the response Paddle received.
notification settings2
- Get notification destinationSource
One notification destination by Paddle ID.
- List notification destinations (webhooks, read only)Source
Notification destinations (webhooks, read only) with cursor pagination (after).
notifications2
- Get notificationSource
One notification by Paddle ID.
- List notifications (webhook deliveries)SourceIncremental
Notifications (webhook deliveries) with cursor pagination (after) and incremental from.
prices4
- Create priceDestinationNot retried automaticallyApproval before production
Creates a price in Paddle Billing.
- Get priceSource
One price by Paddle ID.
- List pricesSource
Prices with cursor pagination (after).
- Update priceDestinationProvider duplicate protectionApproval before production
Updates supplied price fields. Archiving is not automated.
pricing previews1
- Preview pricesSource
Calculates localised totals, tax and discounts for catalog prices without creating anything.
products4
- Create productDestinationNot retried automaticallyApproval before production
Creates a product in Paddle Billing.
- Get productSource
One product by Paddle ID.
- List productsSource
Products with cursor pagination (after).
- Update productDestinationProvider duplicate protectionApproval before production
Updates supplied product fields. Archiving is not automated.
report files1
- Get report CSV linkSource
A temporary link to download a ready report as CSV.
reports2
- Get reportSource
One report by Paddle ID.
- List reportsSource
Reports with cursor pagination (after).
subscription history1
- List history entries of a subscriptionSourceIncremental
History entries of a subscription with cursor pagination (after) and incremental occurred_at[GTE].
subscription previews1
- Preview subscription updateSource
Previews a subscription change (same inputs as Update subscription) and returns the resulting subscription and next renewal totals without applying it.
subscriptions3
- Get subscriptionSource
One subscription by Paddle ID.
- List subscriptionsSource
Subscriptions with cursor pagination (after).
- Update subscriptionDestinationProvider duplicate protectionApproval before production
Updates subscription items, address, business, collection mode, discount and custom data. Changes bill on the next billing period or not at all.
transaction invoices1
- Get transaction invoice PDFSource
A temporary link to the PDF invoice for a billed or completed transaction.
transactions4
- Create draft transactionDestinationNot retried automaticallyApproval before production
Creates a draft or ready transaction (Paddle's invoice or checkout) for catalog prices. Paddle sets the status; Nexra never bills it.
- Get transactionSource
One transaction by Paddle ID.
- List transactions (invoices and payments, read only)SourceIncremental
Transactions (invoices and payments, read only) with cursor pagination (after) and incremental updated_at[GT].
- Update draft transactionDestinationProvider duplicate protectionApproval before production
Updates a draft or ready transaction's customer, address, business, currency, collection mode, discount, billing details, items or custom data. Never changes status.
Access and limits
- 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, report.read, metrics.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 and reports 50) with meta.pagination.next and has_more.
- Provider events
- Paddle notification destinations deliver events such as subscription.updated and transaction.completed; notifications, delivery logs and destinations are readable here. Flows can start the moment something happens: when a payment succeeds; when a payment fails; when a new subscription starts; when a subscription is cancelled.
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 can be created and updated only as drafts or ready transactions: Nexra never sends status, so it never bills, issues or cancels a transaction. Non-catalog prices and custom non-catalog discounts are not offered. Revising billed transactions is not automated.
- Adjustments (credits, refunds and chargebacks) are read only. One-time charges, refunds, credits, trial activation, cancellations, pauses, resumes and payment-method update transactions are intentional exclusions because they move money or end service.
- Saved payment methods are not read or changed: payment-method data is outside the allowed read scope, and deleting them or creating payment-method update transactions is excluded.
- Archiving (status changes) of customers, addresses, businesses, products, prices and discounts is not automated. Discount groups are read only.
- Customer list keeps its existing exact email filter, which Paddle reads from the query string. Prefer the search filter or a customer ID in new flows.
- Report creation, notification destination changes, notification replays, simulations, client-side tokens, customer portal sessions and customer authentication tokens are not offered.
- Transactions support updated_at; notifications and subscription history support occurred-at filters. Other lists are full reads ordered by ID.
- Metrics return daily timeseries points for a date range; Paddle refreshes them periodically (see seriesUpdatedAt).
- Paddle has no usage or metered record API.
- Payouts and payout lines: Paddle pays out as merchant of record, but its API has no payout or settlement list. Payout detail is available only as Paddle's payout reconciliation report (a CSV created in the Paddle dashboard or Reports API); Nexra lists reports and returns a download link for ready reports, but does not create reports.
- Fees: Paddle fees and earnings are fields on transactions (fee and net, plus payoutFee and payoutEarnings in the payout currency) and on adjustments (including chargebackFee).
- Refunds and chargebacks are adjustments (action refund, chargeback, chargeback_warning and their reversals). Paddle's adjustments list has no date filter, so it is a full read ordered by ID; filter by action, status, transaction or customer instead.
- 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
Machine-readable detail: GET /api/public/connect/connectors/paddle and the Connections API.