Paddle
Set up the Paddle connector in AccessLayer.
Paddle is a billing platform for SaaS businesses that manages subscriptions, payments, pricing, reports, and revenue operations.
In AccessLayer, the Paddle connector lets you query customers, products, prices, subscriptions, transactions, discounts, reports, notifications, and related billing metadata for reporting and operational analysis.
Before you start
You will need a Paddle API key and you should know whether you want to connect to live or sandbox data.
Before you begin, make sure you have:
- A Paddle API key
- The correct Paddle environment, live or sandbox
For additional details, see the Paddle authentication documentation.
Use an API key with the right read permissions
Paddle API keys are permission-scoped. Grant the read permissions needed for the resources you want AccessLayer to query, such as customers, prices, products, subscriptions, transactions, discounts, notifications, and reports.
Generating your credentials
Open Paddle authentication settings
In Paddle, go to Developer Tools -> Authentication.
Create an API key
Create a new API key and assign the read permissions needed for the data you want AccessLayer to query.
Copy the API key and confirm the environment
Copy the generated key and note whether you want AccessLayer to use Paddle live or sandbox mode when configuring the connector.
Included collections
- Customers
- Products
- Prices
- Subscriptions
- Transactions
- Adjustments
- Discounts
- Discount Groups
- Events
- Event Types
- Reports
- Notification Settings
- Notifications
- Client Tokens
The connector also includes customer-scoped collections for addresses, businesses, credit balances, and payment methods, plus simulation runs, simulation events, and notification logs.
Troubleshooting
Confirm that the API key is valid and has the read permissions required for the resources you want to query.
Make sure you selected the correct Paddle environment. Sandbox mode returns sandbox data, while live mode returns production data.
Check whether the API key was rotated, revoked, or had its permissions changed. If it changed, create a new key and update the connector configuration in AccessLayer.