Altinn Python API Docs | dltHub

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

Last updated:

Altinn REST APIs start with /api. The Altinn Events API provides endpoints for event publishing and subscription. Altinn Studio Repository API offers OpenAPI specification for Altinn Studio. The REST API base URL is https://platform.altinn.no and all requests require a Bearer token (OAuth2 client credentials).

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


What data can I load from Altinn?

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

ResourceEndpointMethodData selectorDescription
storage_instances/storage/api/v1/instancesGET_embedded.instancesList instances across all applications (Storage API)
storage_instance/storage/api/v1/instances/{instanceId}GETGet metadata for a single instance
storage_instance_data/storage/api/v1/instances/{instanceId}/dataGET_embeddedList data elements for an instance
events/events/api/v1/eventsGETeventsList events published to Altinn Events API
app_instanceshttps://{org}.apps.{env}.altinn.no/{org}/{app}/instancesGET_embedded.instancesApp‑specific instances listing (App API)

How do I authenticate with the Altinn API?

Altinn platform APIs use OAuth2 client‑credentials (Maskinporten) with Bearer tokens; each request must include an Authorization: Bearer <access_token> header.

1. Get your credentials

  1. Register a machine client in Maskinporten (the Norwegian government OAuth2 service). 2) Obtain the client_id, client_secret and required scopes for Altinn platform APIs. 3) Call the Maskinporten token endpoint with grant_type=client_credentials to receive an access_token. 4) Include the access_token in the Authorization header as Bearer <access_token> for all API calls.

2. Add them to .dlt/secrets.toml

[sources.altinn_source] access_token = "<your_maskinporten_access_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 Altinn 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 altinn_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline altinn_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 storage_instances and events from the Altinn 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 altinn_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://platform.altinn.no", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "storage_instances", "endpoint": {"path": "storage/api/v1/instances", "data_selector": "_embedded.instances"}}, {"name": "events", "endpoint": {"path": "events/api/v1/events", "data_selector": "events"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="altinn_pipeline", destination="duckdb", dataset_name="altinn_data", ) load_info = pipeline.run(altinn_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("altinn_pipeline").dataset() sessions_df = data.storage_instances.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM altinn_data.storage_instances LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("altinn_pipeline").dataset() data.storage_instances.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 Altinn 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 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 Altinn?

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