For the complete documentation index, see llms.txt. This page is also available as Markdown.

Netvisor

Complete Netvisor onboarding from your client backend.

Preview · What this means for your integration

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.

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 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. 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

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, including a new UUID in CORRELATION_ID, then send the request once:

3. Check the result

Expect HTTP 201 with source: vismanetvisor and state: completed. Optionally 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.

Last updated

Was this helpful?