NoWaste + Visma.net

Confirm the exact product and environment

Verify the product variant, environment, tenant, and any middleware involved before configuring credentials.

Let Junipeer confirm the auth pattern

Use the agreed Junipeer implementation scope to confirm whether the setup uses API keys, service users, OAuth, tokens, or another method.

Create or receive the technical credentials

Have the system owner, vendor, or implementation partner create the required integration access according to the agreed setup.

Add the credentials in Junipeer

Enter the issued credentials, host details, and any tenant-specific identifiers in the Junipeer admin when requested.

Verify in a non-production environment first

Run a controlled connection test before enabling a live data flow.

Open the Visma.net connector in Junipeer

Start the Visma.net connection from the relevant connector or onboarding step in Junipeer.

Click Connect

Use the connect action in Junipeer to start the Visma Connect sign-in flow.

Sign in with the correct Visma account

Choose the Visma account that has access to the Visma.net environment and company that should be connected.

Approve the requested access

Review the OAuth consent screen in Visma Connect and approve the connection if the account and environment are correct.

Return to Junipeer and verify the connection

After the approval flow completes, go back to Junipeer and make sure the Visma.net connector shows as connected.