This solution also not works as expected. Upto 24 hours API giving new refresh token on every call. After 24hours it again got invalid. This means every users need to re authenticate them self again every year.
... Meer weergeven
Hi Sander, That's true, it is classified as an 'idea' https://community.visma.com/t5/Ideas-in-Developers-Visma-net/Customer-DirectDebitLines-set-brancheId/idi-p/485368
... Meer weergeven
Hi Michel, I have asked for an update from our development team. It might take some time to analyse, because the problem lies partly in the UI. We will keep you posted here.
... Meer weergeven
Alright, if you have a list of the calls, preferably with the request id, and send it together with the clientID to developersupport@visma.com we'll have a look at it and pass it on to the development team.
Thank you.
... Meer weergeven
Hello,
tested the case again today, I'm able to POST Supplier Invoice without receiving Branch not found error. If you're still receiving the error, we might need to specifically check your company & integration setup, so please contact us via developersupport@visma.com and share your companyID & Application details from the developer portal.
Thanks.
... Meer weergeven
Answers given by the VNI support team: Refresh token per user: a new refresh token is obtained by the application for a user when a new authorization request (/connect/authorize) and token request are successful. That will issue a new access token/refresh token pair that counts towards the Refresh token per user configuration. So if your app has a configuration of 20 (max value) it can have max 20 refresh tokens in Visma Connect. Refresh token usage: represents how a refresh token is handled after obtained. Re use - the same refresh token will be returned when calling /connect/token with refresh_token grant type. One time - a new refresh token will be returned each time when calling /connect/token with refresh_token grant type. Refresh token expiration: the expiration is set with two different values Absolute expiration (option The refresh token expiration is set to) is set as a fixed value from the moment when the refresh token was issued (through /connect/authorize). If the "Re use" option is configured the max value can be configured as 180 days. That means the refresh token will expire after that period. If the "One time" option is configured, the absolute expiration can be set to Unlimited which means that the refresh tokens will remain valid if used within the "sliding expiration". Sliding expiration (option But will expire if not used in) is set as a fixed value each time a refresh token is used (through /connect/tolen with grant type refresh_token). Access tokens are not expired: the access tokens are JWTs which have the expiration set as a claim. API access If your app only uses openid, email and profile the access token cannot be used for calling ERP API. When using the tenants scope together with the scopes of the API your app can obtain tenant information from the /connect/userinfo endpoint. The response will contain an array of tenants where the user has access to.
... Meer weergeven
Hi,
There seems to be several cases of this happening, to consolidate all the answers, we wil be posting the answers in this thread
If you still have an issue when we have announced a fix, please do so in the thread and we'll continue from there. Thank you!
... Meer weergeven
Hi Magnus, We use it to set the "Approved for payment" check in the financial details of the invoice. In some cases this happens after the invoice has been released. Now what happend here, with resetting the balance, is a weird one because the end user went of all the normal tracks he is supposed to be and did this all manual and added a payment to it. But the end result is still a bit strange. Thanks, Michel
... Meer weergeven
.gif "VISMA"){kind=icon}
Visma Nederland
Visma Denemarken
Visma Finland
Visma Letland
Visma Noorwegen
Visma Zweden
Visma Developers & Partners
Visma Latijns-Amerika