Linking Klarna as a source
This source is currently in alpha. The interface and available tables may change.
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Alpha: This source is in alpha. Please share feedback in the PostHog community.
The Klarna connector syncs your settlement data – payouts and transactions – into PostHog, so you can reconcile payments and analyze revenue alongside your product data.
Prerequisites
You need a Klarna merchant account with access to the Merchant Portal to create an API key. The key needs read access to the Settlements API.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Klarna, you'll need:
- API key – create one in your Klarna Merchant Portal. Grant the key read access to the Settlements API.
- Username (optional) – for HTTP Basic authentication, enter the UUID supplied with your API key.
- Region – select the region for your merchant account: Europe, North America, or Oceania.
- Environment – choose Live for production data or Playground for testing.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Klarna tables are full refresh only. The Settlements API does not expose filters for incremental syncing, so each sync reloads all data.
Configuration
| Option | Description |
|---|---|
API keyType: password Required: True | |
Username (optional)Type: text Required: False | For HTTP Basic authentication, enter the UUID supplied with your API key. |
RegionType: select Required: True | |
EnvironmentType: select Required: True |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
payouts | Payments from Klarna to the merchant's bank account, with settlement totals. | Full refresh | — | payment_reference |
transactions | Settlement entries for sales, returns, fees, taxes, and adjustments. | Full refresh | — | — |
Troubleshooting
- 401 error: Klarna rejected your credentials. Reactivate or replace the key in the Merchant Portal.
- 403 error: Klarna denied access. Check that your credentials can read settlements in the selected region.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.