Visma Netvisor Python API Docs | dltHub

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

Last updated:

Visma Netvisor is a cloud-based accounting and financial management API providing programmatic access to financial data like customers, invoices, and vouchers. The REST API base URL is https://isvapi.netvisor.fi/ and all requests require HMAC-SHA256 authentication headers with a MAC derived from partner and customer keys.

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


What data can I load from Visma Netvisor?

Here are some of the endpoints you can load from Visma Netvisor:

ResourceEndpointMethodData selectorDescription
customer_listcustomerlist.nvGETCustomerList of customers in the organisation
supplier_listsupplierlist.nvGETSupplierList of suppliers
item_listitemlist.nvGETItemList of inventory items
invoice_listinvoicelist.nvGETInvoiceList of sales invoices
voucher_listvoucherlist.nvGETVoucherList of financial vouchers

How do I authenticate with the Visma Netvisor API?

Authentication uses HMAC-SHA256, where a MAC is computed from a string containing the request URI and several mandatory custom headers. The MAC and other authentication details are passed via specific X-Netvisor-* HTTP headers rather than a standard token.

1. Get your credentials

To obtain credentials for the Visma Netvisor REST API, follow these steps: 1. Join the Visma Netvisor partner program by completing the registration form on their official website to receive partner-specific credentials (Partner ID and Partner Key). 2. For each customer environment, log in to the Netvisor web portal as an administrator. 3. Navigate to the 'Company' menu (or Settings -> Integration) and select 'Api identifiers'. 4. Click 'Create new api identifier' to generate a unique User ID and User Key for the integration. 5. Ensure the software interface service is activated for the company, and configure appropriate access rights for the API resources. Partner support will typically validate the integration before full production use.

2. Add them to .dlt/secrets.toml

[sources.visma_netvisor_source] customer_key = "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 Visma Netvisor 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 visma_netvisor_pipeline.py

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

Pipeline visma_netvisor_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset visma_netvisor_data The duckdb destination used duckdb:/visma_netvisor.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 customerlist.nv and salesinvoice.nv from the Visma Netvisor 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 visma_netvisor_source(customer_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://isvapi.netvisor.fi/", "auth": {"type": "api_key", "api_key": customer_key, "name": "customer_key"}, }, "resources": [ {"name": "customer_list", "endpoint": {"path": "customerlist.nv", "data_selector": "Customer"}}, {"name": "invoice_list", "endpoint": {"path": "invoicelist.nv", "data_selector": "Invoice"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="visma_netvisor_pipeline", destination="duckdb", dataset_name="visma_netvisor_data", ) load_info = pipeline.run(visma_netvisor_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("visma_netvisor_pipeline").dataset() sessions_df = data.customer_list.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM visma_netvisor_data.customer_list LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("visma_netvisor_pipeline").dataset() data.customer_list.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 Visma Netvisor 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 Visma Netvisor?

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

Available Pipelines