> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/onboarding-flow/headless-onboarding/netvisor.md).

# Netvisor

Complete Netvisor onboarding from your client backend.

**Preview** · [What this means for your integration](https://docs.zwapgrid.com/onboarding-flow/headless-onboarding/headless-onboarding.md#preview)

Your backend sends the Netvisor user identifier, customer key and business ID. **Zwapgrid checks company access and completes the connection.** No customer OAuth login is required for this request.

First, complete the [shared prerequisites and example setup](https://docs.zwapgrid.com/onboarding-flow/headless-onboarding/headless-onboarding.md#before-you-start).

## What you need

* The company's **user identifier**, **customer key** and **Finnish business ID**. These are the three values your backend will submit.
* Netvisor interface access enabled for the company and access granted to the intended Zwapgrid integration. Ask Zwapgrid for its integration search key if needed during setup.
* A Published Netvisor System Setting for **Sandbox** or **Production**, belonging to your Zwapgrid client, or a default that Zwapgrid has confirmed your client can use.

Follow the [Netvisor setup guide](https://docs.zwapgrid.com/client-portal/systems/setup-guides/visma-netvisor.md) for interface permissions and environment settings. Zwapgrid manages the integration credentials. You supply the company credentials listed above.

For testing, explicitly select a published Sandbox setting on the Consent. If you omit the selection, confirm which default integration will be used. An invalid selected setting is rejected.

## 1. Prepare the connection

1. Use the [Consent created in the shared workflow](https://docs.zwapgrid.com/onboarding-flow/headless-onboarding/headless-onboarding.md#1-create-a-consent). If selecting settings explicitly, set `systemsSettings.vismanetvisor` to their published ID.
2. Collect the user identifier, customer key and business ID for the company in the selected Netvisor environment.
3. Submit all three values once. Zwapgrid checks access to the company using the selected integration. The business ID selects the company; no additional company-selection request is needed.

## 2. Send the request

```json
{
  "source": "vismanetvisor",
  "credentials": {
    "userIdentifier": "<integration-user-identifier>",
    "customerKey": "<customer-key>",
    "businessId": "<Finnish-business-ID>"
  }
}
```

All three fields are required. `userIdentifier` accepts 1–256 ASCII letters, digits, hyphens or underscores. `customerKey` accepts 1–256 visible ASCII characters without whitespace. Replace `<Finnish-business-ID>` with seven digits, a hyphen and one digit, for example `1234567-8` (format illustration only).

Do not send integration application credentials, codes, redirect URIs, tokens or an environment field. Production/Sandbox selection belongs in System Settings, not this request.

Replace the placeholders and save this body as a protected `connection.json` on your backend. Set the [example variables](https://docs.zwapgrid.com/onboarding-flow/headless-onboarding/headless-onboarding.md#set-up-the-examples), including a new UUID in `CORRELATION_ID`, then send the request once:

```sh
curl --request POST \
  "$CONSENTS_API_BASE_URL/api/v1/consents/$CONSENT_ID/connection" \
  --header "x-api-key: $ZWAPGRID_API_KEY" \
  --header "x-correlation-id: $CORRELATION_ID" \
  --header 'Content-Type: application/json' \
  --data-binary @connection.json
```

## 3. Check the result

Expect HTTP 201 with `source: vismanetvisor` and `state: completed`. [Optionally verify the connection](https://docs.zwapgrid.com/onboarding-flow/headless-onboarding/headless-onboarding.md#optional-verify-the-connection) against the intended company.

After an uncertain POST, use GET before further action; do not automatically replay credentials. For access rejection, confirm the selected integration, company credentials, business ID and interface permissions with the authorized administrator. Contact Zwapgrid with correlation IDs if you cannot confirm whether the connection succeeded. Your backend does not need to exchange or refresh OAuth tokens.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zwapgrid.com/onboarding-flow/headless-onboarding/netvisor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
