Fortnox Python API Docs | dltHub
Build a Fortnox-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Fortnox is a cloud‑based accounting and ERP platform offering a REST API for financial data. The REST API base URL is https://api.fortnox.se/3/ and All requests require an Access‑Token and Client‑Secret header for authentication..
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 pip install "dlt[workspace]" and start loading Fortnox data in under 10 minutes.
What data can I load from Fortnox?
Here are some of the endpoints you can load from Fortnox:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| customers | /customers | GET | Customers | List of customer objects |
| invoices | /invoices | GET | Invoices | List of invoice objects |
| suppliers | /suppliers | GET | Suppliers | List of supplier objects |
| articles | /articles | GET | Articles | List of article (product) objects |
| orders | /orders | GET | Orders | List of order objects |
| currencies | /currencies | GET | Currencies | List of currency objects |
How do I authenticate with the Fortnox API?
Include the Access‑Token header (Bearer JWT, 1 hour expiry) and the Client‑Secret header (provided by your Fortnox app) on every request.
1. Get your credentials
- Log in to the Fortnox developer portal.
- Create a new application to receive a Client ID and Client Secret.
- Set a redirect URI and required scopes.
- Direct a user to the authorization endpoint to obtain an authorization code.
- Call the token endpoint (https://apps.fortnox.se/oauth-v1/token) with the code, client_id and client_secret to receive an access token (JWT, 1 hour) and a refresh token (45 days).
- Store the tokens securely for use in API calls.
2. Add them to .dlt/secrets.toml
[sources.fortnox_source] client_id = "your_client_id" client_secret = "your_client_secret" access_token = "your_access_token" refresh_token = "your_refresh_token"
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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt 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:
dlt ai toolkit rest-api-pipeline install
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 Fortnox 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:
python fortnox_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline fortnox_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset fortnox_data The duckdb destination used duckdb:/fortnox.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline fortnox_pipeline 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 customers and invoices from the Fortnox 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 fortnox_source(client_id=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.fortnox.se/3/", "auth": { "type": "bearer", "token": client_id, }, }, "resources": [ {"name": "customers", "endpoint": {"path": "customers", "data_selector": "Customers"}}, {"name": "invoices", "endpoint": {"path": "invoices", "data_selector": "Invoices"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fortnox_pipeline", destination="duckdb", dataset_name="fortnox_data", ) load_info = pipeline.run(fortnox_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("fortnox_pipeline").dataset() sessions_df = data.customers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM fortnox_data.customers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("fortnox_pipeline").dataset() data.customers.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 Fortnox data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
Troubleshooting
Authentication failures
- Return code 401 with an error payload indicating an invalid or expired Access‑Token. Refresh the token using the refresh token endpoint.
Rate limits
- The API allows 25 requests per 5 seconds (≈300 per minute). Exceeding this returns 429 Too Many Requests. Implement exponential back‑off before retrying.
Pagination
- List endpoints support pagination via
pageandlimitquery parameters. The response includes@CurrentPage,@TotalPages, and@TotalResourcesfields to navigate pages.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Fortnox?
Request dlt skills, commands, AGENT.md files, and AI-native context.