Source connector

PayPal Transactions connector

PayPal Transactions integration for databases, warehouses and BI tools

PayPal transaction history and settlement detail. Datrise captures PayPal Transactions entities such as transactions, payers, balances, fees, refunds and currency conversions, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The PayPal Transaction Search API v1 authenticates with OAuth 2.0, incremental runs key on start_date / end_date.

Of the 6 objects, 4 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `paypal_transaction_transactions`) with a schema derived from the PayPal Transactions API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the PayPal Transactions pipeline page, and join the waitlist to get the PayPal Transactions connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What PayPal Transactions data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
transactions	paypal_transaction_transactions	Append-only, incremental by timestamp
payers	paypal_transaction_payers	Upsert by primary key, incremental on updated-at
balances	paypal_transaction_balances	Upsert by primary key, incremental on updated-at
fees	paypal_transaction_fees	Upsert by primary key, incremental on updated-at
refunds	paypal_transaction_refunds	Append-only, incremental by timestamp
currency conversions	paypal_transaction_currency_conversions	Upsert by primary key, incremental on updated-at

PayPal Transactions API: setup facts for the connector

Verified against the vendor documentation on 2026-09-03. Unknown values are left blank rather than guessed.

API	PayPal Transaction Search API v1
Authentication	OAuth 2.0 — OAuth 2.0 client-credentials: the app's client ID and secret are exchanged for an access token sent as a Bearer token.
Pagination	page — `page` and `page_size` on `GET /v1/reporting/transactions`; `page_size` accepts values from 1 to 500.
Rate limit	Not published
Incremental cursor	start_date / end_date — The window itself is the cursor — a request covers at most 31 days, so an incremental sync advances `start_date` to the previous `end_date` each run.
Webhooks	Yes — PayPal Webhooks (REST event notifications)
Bulk export	No
Deletes detectable	Not published

Official API reference

What bites when replicating PayPal Transactions

A single list-transactions call supports a maximum range of 31 days, so a full three-year backfill is at least 36 sequential windowed requests rather than one paged read.
Only the previous three years of transactions are reachable through this API; anything older cannot be retrieved at all and has to come from a downloaded report.
It takes up to three hours for an executed transaction to appear in the list-transactions call, so a sync that reads right up to `now` silently misses the most recent rows.
`page_size` accepts 1 to 500 but PayPal's own example uses 20, so a client copied from the docs makes 25 times more calls than it needs to.

Compare this against every other documented API

Popular destinations for PayPal Transactions

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

PayPal Transactions connector FAQ

What PayPal Transactions data does the connector extract?: 6 objects: transactions, payers, balances, fees, refunds and currency conversions. Each lands in its own table with types preserved; history-style objects (2: transactions and refunds) load as append-only streams.
Is the PayPal Transactions integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load PayPal Transactions data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each PayPal Transactions → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your PayPal Transactions pipeline with guided onboarding

Join the waitlist to get priority access for PayPal Transactions integrations with guided setup, schema-aware mapping, and production-grade incremental sync.