Recently, the Swagger on https://integration.visma.net/API-index/doc/swagger has been updated. Since then, the tokenUrl and authorizationUrl point to the wrong server. The current definition points to "
Solved! Go to Solution.
While we are waiting for a solution as a sidenote/workaround, you only need to authorize once with your API user as there is no time limit/need to refresh the token in Visma.Net authorization.
If you have authorized once, for all companies the user has access to, it will be valid, as it is written in the documentation that is provided in the ISV certification program.
Thanks for the suggestion.
The problem with your suggestion is twofold:
- New users don't have tokens yet, so they have to use this flow.
- Some of our products work client-side. We do not save refresh tokens there for security reasons. I would also suggest Visma to add the implicit grant flow which is more suitable for client-side applications.
So in short: your suggestions are unfortunately not going to work for our current users. We really need the Swagger updated.
Rrgarding ideas for Visma.Net Financials, we have a section where you can post these: Ideas
There improvements can be posted and voted on by the community.
As mentioned, for now we are waiting for the development team to have a look at this issue, however the addresses provided in the documentation(attached here again for ease) are still valid.
I don't doubt the hand-written documentation is correct at this point in time. However, Visma has provided a technical documentation in the form of a Swagger definition that now deviates from the hand-written documentation.
Do you want to say that we should only use the hand-written documentation for this type of information, or do you think the Swagger should (also) be correct at all times?
Copyright © 2019 Visma.com. All rights reserved.