Hi Adrian,   Thanks for you input. Unfortenately I can't keep a client secret secured, that why I use a native app. Still think that the expiration period of a refresh token should be sliding since last use instead compared to the first user consent.   Best regards, Sander     ... Meer weergeven

Got it, we'll put another reminder to the case and will be following the status.  ... Meer weergeven

Batch does not give you a transaction and the parts run sequentially on the server anyway so there is not much  performance difference. Parallel requests are always faster Thanks for the insights. It's completely useless then. I'll just send requests in parallell - that works just fine. ... Meer weergeven

Hi! The error message should contain what policy triggered it. Example: HTTP Status: 429 Exception Message: "Same request made too many times" Response Headers: x-ratelimit-limit: 5 x-ratelimit-policy: IntervalLimit x-ratelimit-reset: 1551868340 (Epoch-Unix Format which is representing the start of next sliding window)   You can see the different policies in this article: Why am I receiving "HTTP 429 - Too many request / throttling" response from API ? ... Meer weergeven

After the fix, this will be working as described, auto-increment sequential numbers. (1-2-3 instead of 2-4-6) "lineNumber" doesn't have any effect in the POST operations, and it'll be automatically increased by as many lines as included in the transaction. ... Meer weergeven

Hello,  this has been planned to be implemented in Visma.net Financials API updates for version 8.74.0 (November 2021) ... Meer weergeven

Hi, Good suggestion, we'll look into getting this sorted.   Thank you.  ... Meer weergeven