Swish Python API Docs | dltHub

Build a Swish-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Swish is a Swedish mobile payment platform providing a Commerce API for handling payment requests and refunds securely via TLS-based authentication. The REST API base URL is https://mss.cpc.getswish.net/swish-cpcapi/api/v2 and all requests require mutual TLS (mTLS) authentication using a client certificate.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Swish data in under 10 minutes.


What data can I load from Swish?

Here are some of the endpoints you can load from Swish:

ResourceEndpointMethodData selectorDescription
payment_requests/swish-cpcapi/v2/paymentrequests/{id}GETRetrieve a specific payment request by ID
refunds/swish-cpcapi/v2/refunds/{id}GETRetrieve a specific refund by ID
payouts/swish-cpcapi/v2/payouts/{id}GETRetrieve a specific payout by ID
payment_requests_create/swish-cpcapi/v2/paymentrequestsPOSTCreate a new payment request
refunds_create/swish-cpcapi/v2/refundsPOSTCreate a new refund

How do I authenticate with the Swish API?

The Swish Commerce API utilizes mutual TLS (mTLS) for authentication. Requests must be authenticated using a client-side certificate (typically provided as a .p12 file) to secure the connection between the client and the Swish server.

1. Get your credentials

To obtain credentials for the Swish Commerce API, you do not use a standard API key. Instead, you must use a client TLS certificate. 1. Contact your bank to enroll in the Swish Commerce service and authorize a Certificate Point of Contact (CPOC). 2. Generate an RSA key pair and a Certificate Signing Request (CSR) on your server. 3. Log in to the Swish Certificate Management portal (https://comcert.getswish.net/) using Mobile BankID, BankID on card, or BxID. 4. Navigate to the New certificate section, provide your organizational number and Swish number, and submit your CSR. 5. Download the issued client certificate, which is used for mutual TLS (mTLS) authentication when making API requests.

2. Add them to .dlt/secrets.toml

[sources.swish_source] swish_cert_path = "/path/to/your/client_certificate.p12" swish_cert_password = "your_certificate_password" swish_ca_cert_path = "/path/to/swish_root_ca.pem"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Swish API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python swish_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline swish_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset swish_data The duckdb destination used duckdb:/swish.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads paymentrequests and refunds from the Swish API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def swish_source(client_certificate=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://mss.cpc.getswish.net/swish-cpcapi/api/v2", "auth": {"type": "bearer", "token": client_certificate}, }, "resources": [ {"name": "payment_requests", "endpoint": {"path": "swish-cpcapi/v2/paymentrequests/{id}"}}, {"name": "refunds", "endpoint": {"path": "swish-cpcapi/v2/refunds/{id}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="swish_pipeline", destination="duckdb", dataset_name="swish_data", ) load_info = pipeline.run(swish_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("swish_pipeline").dataset() sessions_df = data.payment_requests.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM swish_data.payment_requests LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("swish_pipeline").dataset() data.payment_requests.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Swish data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Swish?

Request dlt skills, commands, AGENT.md files, and AI-native context.