There is currently a large incident on the Visma.net APIs. The cause is yet unclear and it is unclear whether this is a bug in the Visma.net APIs or an undocumented breaking change.
An error with the same cause can be:
itgenvnt033
Invalid parameter exception: ipp-company-id (12002_12002_7b28d6d8-104b-4acc-991b-e5290bde8fdb)
For details, please subscribe to the follwing incident:
A related topic is:
It might be that unexpectedly the expected changes for moving from VNI Authentication to Visma Connect Authentication have been taken into production. It is unclear whether this is intended or a release error; as soon as known we will update this post.