Every month our customer sends an API call to General Ledger of approximately 13,500 lines. Previously this took approximately 45 minutes. Since last week they have received 500 reports. We have already divided the post into parts of 500 lines. Sometimes things go well now, but it takes upto 20 minutes per call, or we get error 500. ... View more

Hi, We are aware and are looking into it: https://status.visma.com/incidents/xj1qjw02p3w4 ... View more

Hi, We are aware and are looking into it: https://status.visma.com/incidents/xj1qjw02p3w4 ... View more

Hi, We are aware and are looking into it: https://status.visma.com/incidents/xj1qjw02p3w4 ... View more

I've sent a few examples to developersupport now ... View more

+1 on this from us as well, we are getting this message several times each day for different tenants on different endpoints for the last couple of days, like generalledgertransactions, customercreditnote and generalledgerbalance. We are using clientId/tenantId as well and are checking the expiration time of the token before each call. ... View more

The problem is back since about 15 minutes ago... Can you look into it as soon as possible?   ... View more

Thanks for the confirmation Jolu  ... View more

Hi, Thank you, that sounds like the way to go! Best regards Johan Lundqvist ... View more

Hi,   How about adding these kind of limitations to the API-documentation, we also discovered this by chance and would have found it a bit earlier if it was in the documentation? ... View more

Further instructions regarding company "2730***" has been sent via email.  ... View more

Hello Johan,    "Since the last errors happened almost at the same time for all of our customers I don't think there are any issues with either the company access or the licenses and the integration starts to work again after a while without any user intervention. Could you please check on your side again why these errors occurs and if they are safe to ignore in most cases? "   We've not seen anything abnormal with those companies (18545**)  (20824**)  (36721**) The reason that you might have received the mentioned error with all the companies on December 8th is due to the scheduled maintenance <https://status.visma.com/incidents/pbl1mmvcyq5f> since Visma.net Financials & Logistics, Payroll & HRM services were not available during the window so that they cannot be accessed.    Please let us know if you receive the same error again, sharing information about the instance such as  -CompanyID - Authenticated User during Token Generation <xxx@xxx.com> -Error Message    Apart from the times that Services are unavailable and although you've mentioned that "the integration starts to work again after a while without any user intervention" It's still worth checking the "licence in use / allowed numbers" in the issue occurred companies.   Connecting your Visma.Net Financials company to the API   This is possible that if a new user granted access to those companies where its licence exceeded and then revoked the access so that it was continuing to working as expected. Thanks.  ... View more

Hi, Please follow this status page: https://status.visma.com/incidents/8b8nvbg7fqjm   This is currently being investigated. ... View more

Hi again,   Is there a way to get around this issue in some way until you have found the problem, according to the documentation it is not possible to filter the fetching by financial period or creation date ranges but maybe there are some not documented way of doing this? Using lastModifiedDateTime isn't really an option when you try to get the complete set of data since that doesn't support range either.   Best regards Johan ... View more

Hi,   Thank you for the feedback! ... View more

Thank you, I have sent an e-mail! ... View more