Renta / Docs / Sources / Paddle

Paddle

Renta exports six Paddle objects to your data warehouse: customers, products, prices, subscriptions, transactions with their payments and line items, and adjustments that cover refunds, credits, and chargebacks.

You choose the fields of each object yourself. Every run re-reads the full list of records from Paddle, so the tables follow the current state of your account: new records, status changes, and edits arrive with the next run.

Authentication

Renta connects to Paddle with an API key. You create the key in the Paddle Dashboard under Developer tools > Authentication and paste it into the connection form.

When creating the key, grant it read permission for the entities you plan to export. Renta verifies the key by reading the product list, so a key without read permissions fails when you save the connection.

Renta reads the live environment of your Paddle account. Sandbox accounts use separate API keys and are not supported.

Connect Paddle source

Follow these steps to add Paddle as a source in Renta using your API key.

Go to the CatalogStep 1
  1. Navigate to the Connections > Catalog section in the left sidebar.
  2. Open the Finance category and click the Paddle card.
Paddle card in the Finance category of the Renta catalog
Fill in the connection formStep 2
  1. Source name.
    A display name for this connection. It is used exclusively in the Renta interface.
  2. API key.
    Paste the API key from your Paddle Dashboard.
Add a new Paddle connection page with the Source name and API key fields
Save the connectionStep 3
  1. Check the Source name.
  2. Click Save.

Renta verifies the key with Paddle before saving the connection, so an invalid key, or a key without read permissions, fails on this step.

Paddle connection setup with the source name filled in and the Save button
Source createdStep 4

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Sources list with the new Paddle source in the Active status

Create a pipeline

Once the source is connected, create a pipeline to sync your Paddle data into your destination.

Create a Paddle pipeline

Link your Paddle source to a destination and configure the pipeline.

Select Paddle as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select Paddle in the list and click Next step.

Select a source step with Paddle in the list of sources
Select your Paddle connectionStep 2

Choose the Paddle connection you created earlier and click Next step. The card shows the name of the connection and the date it was added.

Select your Paddle connection step with the connection card and its creation date
Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery under Already connected
Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step. The card shows the dataset and project the data will land in.

Select your Google BigQuery connection step with the dataset and project identifiers on the card

Pipeline configuration

On the final step, choose the report type, pick its fields, name the table, and set the schedule.

Report type

Select which Paddle object the pipeline exports. One pipeline loads one report type.

Paddle pipeline settings with the Report Types dropdown open
Report typeDescription
CustomersCustomers of your account: name, email, status, locale, marketing consent, and your custom data.
ProductsThe product catalog: name, description, type, status, tax category, and image URL.
PricesPrices attached to products: unit amount and currency, billing cycle, quantity limits, trial period, tax mode, and country-specific price overrides.
AdjustmentsRefunds, credits, and chargebacks: action, status, reason, totals in the transaction and payout currencies, and the per-item breakdown.
SubscriptionsSubscriptions with their status, billing cycle, the start, first billing, pause, and cancellation dates, the subscription items, the discount, and the scheduled change.
TransactionsThe billing history of the account: status, origin, invoice number, totals before and after adjustments in the transaction and payout currencies, line items, tax rates, and payment attempts.

Parameters

Select the Paddle fields to include in the destination table.

Paddle parameters picker with the Parameters and Selected tabs and the Unselect All button

Below each field is the name its column takes in the destination table. To select every field at once, click Select All. The Selected tab lists everything you picked.

Paddle reports monetary amounts as strings in the smallest currency unit, and Renta loads them as is: a payment of $100.00 arrives as 10000. Cast these columns to a number in your queries. Timestamps arrive as regular datetime columns, and Created Date At is a ready-made date version of the creation timestamp.

Fields that hold a list of values load as nested records.

Report typeFields that load as nested records
AdjustmentsItems, Tax Rates Used
SubscriptionsItems
TransactionsItems, Details Line Items, Details Tax Rates Used, Payments

The Custom Data field arrives as a JSON string with the keys you set in Paddle. Several fields with a variable structure arrive the same way: the trial period and price overrides of a price, the discount and scheduled change of a subscription, the billing details of a transaction, the price inside transaction items, and the payment method details inside payments. Extract their keys with the JSON functions of your warehouse.

Table name

Name the destination table. You can keep the auto-generated name or enter your own. For a data lake destination, this becomes the folder name.

Schedule

Choose how often the pipeline runs.

Paddle schedule type selection with the Daily option checked
Schedule typeDescription
ManualThe pipeline runs only when triggered manually through the interface or via API.
DailyThe pipeline runs once a day at the specified update time.
IntervalThe pipeline runs at specified time intervals.
Cron ExpressionThe pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time, the exact time each run starts, then click Create pipeline.

Update time selection and the Create pipeline button

Renta also supports API triggers and integration with external orchestrators such as Apache Airflow, Dagster, and Prefect. See the full scheduling documentation for details.

The new pipeline appears in the Pipelines section under the ETL tab, where you can track its runs, progress, and the destination table name.

Pipelines list with the new Paddle integration in the Completed status

Sync strategy

Every Paddle report type works in full reload mode.

StrategySupported report typesDescription
Full reloadCustomers, Products, Prices, Adjustments, Subscriptions, TransactionsThe Paddle API returns the current state of every record. Renta reads the full list of the selected object on each run and replaces the contents of the destination table, so the table mirrors the account at the moment of the run. Changes made in Paddle after a record was loaded arrive with the next run.

The pipeline has no date range: a run always covers the whole history of the object. The more records the account holds, the longer a run takes.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.