KSEF API Python API Docs | dltHub

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

Last updated:

The National System of e-Invoices (KSeF) API allows taxpayers to issue, receive, and store structured invoices programmatically. The REST API base URL is https://api.ksef.mf.gov.pl/v2 and requests require a Bearer token in the Authorization header.

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 KSEF API data in under 10 minutes.


What data can I load from KSEF API?

Here are some of the endpoints you can load from KSEF API:

ResourceEndpointMethodData selectorDescription
active_sessions/api/v2/auth/sessionsGETGet list of active sessions
sessions/api/v2/sessionsGETGet list of sessions matching criteria
session_invoices/api/v2/sessions/{referenceNumber}/invoicesGETGet invoices for a session
session_details/api/v2/sessions/{referenceNumber}GETGet details of a session
invoice_metadata/api/v2/invoices/query/metadataPOSTQuery metadata of invoices

How do I authenticate with the KSEF API API?

Authentication is a multi-step process involving a challenge, encryption, and token redemption. After obtaining a session token, include it in the 'Authorization' header as a 'Bearer' token.

1. Get your credentials

  1. Navigate to the official KSeF Taxpayer Application portal at https://ksef.mf.gov.pl/. 2. Log in using a qualified electronic signature (kwalifikowany podpis elektroniczny) or a Trusted Profile (Profil Zaufany). 3. Ensure the login is performed by a person authorized to represent the company (e.g., a management board member listed in the KRS register). 4. Navigate to the 'Zarządzanie tokenami' (Token Management) section within the portal. 5. Click 'Generuj token' (Generate token). 6. Provide a descriptive name for the token, select the required permissions (e.g., 'invoicing' for sending/receiving invoices), and set the validity period (up to 365 days). 7. Copy and securely store the generated KSeF token, as it will be required for configuring your integration.

2. Add them to .dlt/secrets.toml

[sources.ksef_api_source] token = "REPLACE_ME"

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 KSEF API 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 ksef_api_pipeline.py

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

Pipeline ksef_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset ksef_api_data The duckdb destination used duckdb:/ksef_api.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 auth/challenge and auth/ksef-token from the KSEF API 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 ksef_api_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.ksef.mf.gov.pl/v2", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "active_sessions", "endpoint": {"path": "api/v2/auth/sessions", "data_selector": "invoices"}}, {"name": "sessions", "endpoint": {"path": "api/v2/sessions", "data_selector": "invoices"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ksef_api_pipeline", destination="duckdb", dataset_name="ksef_api_data", ) load_info = pipeline.run(ksef_api_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("ksef_api_pipeline").dataset() sessions_df = data.sessions.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM ksef_api_data.sessions LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("ksef_api_pipeline").dataset() data.sessions.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 KSEF API 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 KSEF API?

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

Available Pipelines