Load Visma Netvisor data to DuckDB

Visma Netvisor is a cloud-based accounting and financial management API providing programmatic access to financial data like customers, invoices, and vouchers. Everything needed to build a working Visma Netvisor → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Visma Netvisor to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Visma Netvisor to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Visma Netvisor API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Visma Netvisor API at a glance

These values come from the Visma Netvisor API reference — the authoritative source if anything here looks out of date.

---

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

Copy
[sources.visma_netvisor_source]
customer_key = "REPLACE_ME"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Visma Netvisor data can I load into DuckDB?

These are the Visma Netvisor endpoints dlt can load into DuckDB:

---

How do I load only new Visma Netvisor records?

Visma Netvisor exposes updated_at on customerlist.nv, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "customer_list", "endpoint": {
    "path": "customerlist.nv",
    "data_selector": "Customer",
    "incremental": {"cursor_path": "updated_at", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Visma Netvisor pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading customerlist.nv and salesinvoice.nv from the Visma Netvisor API into DuckDB:

Copy
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 load_visma_netvisor_to_duckdb() -> 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)


if __name__ == "__main__":
    load_visma_netvisor_to_duckdb()

Run it with python visma_netvisor_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Visma Netvisor data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("visma_netvisor_pipeline").dataset()
df = data.customer_list.df()
print(df.head())

SQL:

Copy
SELECT * FROM visma_netvisor_data.customer_list LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Visma Netvisor to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Visma Netvisor loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Visma Netvisor data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack