Invalid_tenant on registration Visma.net database using Visma Connect (itgenoda822 or itgenvnt059)

[tte38]

When I use a new database defined with “Use VNI” I continously get error message upon data retrieval:

itgenvnt067
You are out of API requests.
Retry after 411 seconds.

When I try to register a new database with Visma Connect instead of VNI (Visma Net Interface) I get the following error on registration:

invalid_tenant
Data access requires an active OAuth access token.
A new access token could not be acquired by exchange…

How do I resolve this problem?

[forums]

As described in Migrating from Visma.net ERP Integrations (VNI) to Visma Connect for Visma.net, Visma is obsoleting VNI and replacing it by Visma Connect.

Fix invalid_tenant on Visma Connect

Your use of Visma Connect can require some changes.

When the error invalid_tenant occurs, your admin needs to provide your Visma.net user with additional privileges in the Admin menu from https://home.visma.com:

Next go the “Users and roles” menu and select the Visma.net user.

Then make sure that the “API User” as highlighted below with the red arrow has been granted:

If not, grant the “API User” privilege.

It can allegedly take 10-15 minutes before the change becomes active. Therefore wait 15 minutes first.

Then try again to register the database.

Multi-company

Please note that Visma Connect introduces a large breaking change for multi-company access. Read Migrating from Visma.net ERP Integrations (VNI) to Visma Connect for Visma.net for more details.

Error code

The error code invalid_tenant can be replaced in future versions by either itgenoda822 and/or itgenvnt059 to ease resolution.

The accompanying message text is:

The application user or subscription is not entititled to use the API.
The remote server returned an error: (400) Bad Request.
Please ensure the license allows API access and ensure that the application user has the necessary roles to use the API.

[forums]

This question was automatically closed after at least 1 week of inactivity after a possible solution was provided. The last answer given has been marked as a solution.

Please ask a new question via a separate topic if the problem occurs again. Please include a link to this topic in the new question by pasting its URL into the text.