Visma netvisor

Visma Netvisor (via Apideck)

Access Visma Netvisor through Apideck's Accounting unified API — one of 34 Accounting connectors that share the same method surface. Code you write here ports to Access Financials, Acumatica, banqUP and 30 other Accounting connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Visma Netvisor plumbing.

Beta connector. Visma Netvisor is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.

Quick facts

• Apideck serviceId: visma-netvisor
• Unified API: Accounting
• Auth type: custom
• Status: beta
• Gotchas: page
• Visma Netvisor docs: https://support.netvisor.fi
• Homepage: https://netvisor.fi/accounting-software/

When to use this skill

Activate this skill when the user explicitly wants to work with Visma Netvisor — for example, "create an invoice in Visma Netvisor" or "reconcile payments in Visma Netvisor". This skill teaches the agent:

1. Which Apideck unified API covers Visma Netvisor (Accounting)
2. The correct serviceId to pass on every call (visma-netvisor)
3. Visma Netvisor-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

• apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

• Accounting: https://specs.apideck.com/accounting.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List invoices in Visma Netvisor
const { data } = await apideck.accounting.invoices.list({
  serviceId: "visma-netvisor",
});

Portable across 34 Accounting connectors

The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from Visma Netvisor to another Accounting connector is a one-string change — no rewrite, no new SDK.

// Today — Visma Netvisor
await apideck.accounting.invoices.list({ serviceId: "visma-netvisor" });

// Tomorrow — same code, different connector
await apideck.accounting.invoices.list({ serviceId: "access-financials" });
await apideck.accounting.invoices.list({ serviceId: "acumatica" });

This is the compounding advantage of using Apideck over integrating Visma Netvisor directly: code against the unified Accounting API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

Visma Netvisor via Apideck Accounting

Visma Netvisor is a Finnish financial management platform under the Visma Group, popular with Finnish SMBs and service businesses.

Entity mapping

Netvisor entity	Apideck Accounting resource
Sales Invoice	invoices
Purchase Invoice	bills
Customer	customers
Supplier	suppliers
Credit Note	credit-notes
Payment	payments
Item	invoice-items
Purchase Order	purchase-orders
Journal	journal-entries

Coverage highlights

• ✅ Sales and purchase invoices
• ✅ Customers, suppliers
• ✅ Credit notes, payments
• ✅ Purchase orders
• ✅ Journal entries
• ✅ Finnish VAT
• ❌ Finnish-specific regulatory submissions — use Proxy
• ❌ Payroll — separate Visma product

Auth notes

• Type: Custom (Netvisor-specific signed-request auth), managed by Apideck Vault
• Company binding: one Netvisor company per connection. Netvisor identifies companies via Business ID (Y-tunnus).
• Sender credentials: Apideck's Vault app handles sender key rotation; end-user provides their Netvisor partner credentials.
• Finnish compliance: Netvisor is certified for Finnish accounting standards (Kirjanpitolaki).

Example: list open invoices

const { data } = await apideck.accounting.invoices.list({
  serviceId: "visma-netvisor",
  filter: { status: "open" },
});

Escape hatch: Proxy API

When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Visma Netvisor directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Visma Netvisor's own API:

curl 'https://unify.apideck.com/proxy' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}" \
  -H "x-apideck-consumer-id: ${CONSUMER_ID}" \
  -H "x-apideck-service-id: visma-netvisor" \
  -H "x-apideck-downstream-url: <target endpoint on Visma Netvisor>" \
  -H "x-apideck-downstream-method: GET"

See Visma Netvisor's API docs for available endpoints.

Sibling connectors

Other Accounting connectors that share this unified API surface (same method signatures, just change serviceId):

access-financials (beta), acumatica (beta), banqup (beta), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, and 25 more.

See also

• Accounting OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• Visma Netvisor official docs