Integrations / Paddle
Paddle
Paddle merchant-of-record payments platform for customers, products, prices, subscriptions, transactions, and discounts.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
Paddle API key from Paddle > Developer Tools > Authentication. Scope the key's permissions to the resources these tools need (customer, product, price, subscription, transaction, discount). Live keys only work against https://api.paddle.com; Sandbox keys only work against https://sandbox-api.paddle.com. Store base_url=https://sandbox-api.paddle.com with the credential to target Sandbox — omitted, requests go to Live.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- API key
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Customer | Partial — not every record the vendor holds is synced |
| Product | Partial — not every record the vendor holds is synced |
| Subscription | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Customer | Up to 1 day | Removed records disappear on the next full sync |
| Product | Up to 1 day | Removed records disappear on the next full sync |
| Subscription | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Customer, Product, Subscription.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty