Search
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Sign In
My Products
Help
Sign in or create account
to get a personalized navigation.
Sign in or create account
to get a personalized navigation.
User Profile
JoLu
41
Posts
2
Kudos
1
Solution
18-11-2024
08:06
Hi, We are still seeing these errors, one of them from this morning: {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_1c2cd972-4c1c-401b-9ae5-88020e219396","ExceptionDetails":""} Are you looking into this or do you know what the problem is?
... View more
06-11-2024
10:54
We are also seeing these errors, getting more and more of them today, like {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_2fe64907-c623-4721-9919-e00a6b3e1a81","ExceptionDetails":""}
... View more
08-12-2023
09:06
Same for us, all our integrations are failing with Bad Gateway, again.
... View more
26-10-2023
07:50
As an addition to the previous reported errors we have also started to get null results for calls that previously returned empty arrays or data in responses. Like for calls to controller/api/v1/subaccount that returns null value for Segments, it is also not happening all the time but occasionally and when retried it is not null for the same customer.
... View more
24-10-2023
10:39
At the moment it is only for one customer, we get 5520, latest with id 5520_4c01ee49-a2fa-4411-813d-190957d1c4d7 for endpoint financialPeriod.
... View more
24-10-2023
09:55
Still getting 5520, the latest at 09:50, 5520_9095fde0-8ffb-4a13-8a8e-2d4d88ef1ef9
... View more
24-10-2023
08:11
We still get 5520, the latest at 08:00 for financialPeriod, exception message id 5520_0efb4a43-66d1-448c-9fa6-323d2613c7c5
... View more
24-10-2023
07:47
1 Kudo
And we are also still getting 5520 errors, and now also 502, 503 and 404 errors from several endpoints. The latest errors at 07:44.
... View more
23-10-2023
11:36
We are also experiencing a lot of 5520 errors on multiple endpoints and for multiple customers.
... View more
05-05-2023
13:32
+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
27-03-2023
20:34
We also get these errors, have seen it since about 14 and it still is an issue 6 hours later.
... View more
20-02-2023
13:36
Hi, I can see that the issue has been fixed and that the Tenant-ID can be seen and copied in the App store now. Thanks.
... View more
13-02-2023
10:03
I think I need to clarify the question a bit considering the answers, it is all really good that we can see the Tenant-ID:s of the added companies in the developer portal and that we get notified about added companies but we have a solution that has tens of thousands of companies (not all Visma.Net companies though) and we can't manually monitor the added companies and add the Tenant-ID:s to the correct configuration for the companies so we rely on customers being able to copy and and add those to the solution themselves, thats why it is important that they can see and copy that in an easy way.
... View more
13-02-2023
07:56
Hi, The issue can even be seen in your own guide but here is a print screen as well: Seeing the Tenant-ID in the developer portal is a good thing but if the customer can't enter it since they can't copy it we will never get it into the portal.
... View more
08-02-2023
16:34
In the guide for moving to Visma Connect Authentication there is a part about how the end user can get the tenant-id that must be used in a service to service integration: "For non-interactive applications the context needs to be decided when creating the token, this is done by sending in the tenant-id as part of the token request. Then tenant-id is unique for each company and can be found by the customer in the Visma App Store." There is a problem with this since in the App Store the tenant-id can't be easily copied by the end user since it is truncated in the UI, is that something that you could check if it can be fixed?
... View more
25-01-2023
13:00
Hi, Thank you, that sounds like the way to go! Best regards Johan Lundqvist
... View more
24-01-2023
15:01
Hi, Yes we have implemented the integration according to the articles and are able to connect without any issues but would like to be able to verify that the connection is made for the correct company so the question is if there is any way of getting the company information from the API using the service to service connection? Best regards Johan Lundqvist
... View more
24-01-2023
13:49
Hi, We are moving our solution to the new Visma Connect Authentication and wonder how we can get the company info back from the API, we are in our current solution retrieving the company info so that we can validate that the user have connected to the correct company by comparing organization number but that seems to be unavailable when using Visma Connect? Best regards Johan Lundqvist
... View more
07-12-2022
10:19
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
15-12-2021
11:35
Hi, We still get timeouts now and then even for requests that only fetches updated entities and the company 2730*** could still not be fetched at all.
... View more
09-12-2021
19:37
Without success means that we haven't been able to get a complete set of data for three years for the company, we fetch financial years, accounts, account balances, cost centers, projects, general ledger data, customer and supplier invoices and it has failed in one or more of these areas in every try we have made. We do retries for every request (page) up to five times with an increasing back-of time until we get the data or the request times out, which is set to 20 minutes per request, and then we consider it to have failed.
... View more
09-12-2021
16:18
When testing the calls I saw that there where about 2300 customer invoices for the period 202101 and it seemed that it is more or less the same for other periods as well, so that would mean about 23 pages for that period, and we are trying to get data for three years in total. For supplier invoices there are about 14000 invoices and we are currently trying to get them using a page size of 500. The timeout can happen on any page, this morning I tried the same call and that timed out but now when testing it takes somewhere between 15 and 30 seconds for customer invoices.
... View more
09-12-2021
15:17
We have tried to fetch data for that specific company since 2021-12-06 without success.
... View more
09-12-2021
13:28
Hi, The biggest issue is for a company with Id 273**** which we can't fetch data for due to timeouts but the issue exists for several customers but that is manageable at the moment since for them we only have to get the changed data as of now. The performance is not always bad, it varies very much and sometimes a call may take 17 seconds but the next time it is tried it won't return anything before the 20 minute timeout.
... View more
09-12-2021
10:27
1 Kudo
Hi,
We are still seeing problems with performance and timeouts in the API, fetching customer invoices can take several minutes for one page of 100 invoices (if it even can be fetched before the timeout of 20 minutes that we are using). Could you please check if there are any issues with the API.
Best regards
Johan
... View more
08-12-2021
18:19
Hi, Thank you for your answer. 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? Best regards Johan
... View more
08-12-2021
11:39
Hi, We have experienced these kind of errors and others as well since we started to use the API but they seem to happen more frequent nowadays. As I wrote in the initial post the last time we experienced these issues was 2021-12-08 00:35 (UTC). I have sent examples of the latest errors to developersupport@visma.com. Best regards Johan
... View more
08-12-2021
09:53
We get error messages from the API almost every day for our integration, on all our connected customers and on different endpoints, sometimes several times each day. Most of the times there are no real issues and even if the error messages indicates problems with tokens etc it works if we retry the requests after a while without doing any new authentication etc. Examples of the errors we get from the API are: - Exception while trying to validate user context in ODP based on token. - Invalid parameter exception: companyInContext Is these error messages something that we can ignore or may there be situations where they actually indicates real errors? We are using a retry policy for our requests so that we retry erroneous request up to five time with an increasingly longer wait period between the requests before we stop trying and signals an error but even with these retries if fails. The last time we experienced these issues was 2021-12-08 00:35 (UTC). Best regards Johan
... View more
Activity Feed for JoLu
- Posted Re: Increase in errors the last days on Forum in Developers Visma.net. 18-11-2024 08:06
- Posted Svar: Increase in errors the last days on Forum in Developers Visma.net. 06-11-2024 10:54
- Kudoed Bad Gateway messages when making calls to the Visma.Net ERP API for Ronald de Jong. 08-12-2023 09:17
- Posted Svar: URGENT. Bad Gateway 502 in multiple integrations on Forum in Developers Visma.net. 08-12-2023 09:06
- Kudoed URGENT. Bad Gateway 502 in multiple integrations for Gabriella Hennings. 08-12-2023 09:06
- Posted Svar: 5520 on Forum in Developers Visma.net. 26-10-2023 07:50
- Posted Re: 5520 on Forum in Developers Visma.net. 25-10-2023 08:42
- Posted Re: 5520 on Forum in Developers Visma.net. 24-10-2023 10:39
- Posted Re: 5520 on Forum in Developers Visma.net. 24-10-2023 09:55
- Posted Re: 5520 on Forum in Developers Visma.net. 24-10-2023 08:11
- Kudoed Sv: 5520 for andreasaulin. 24-10-2023 07:58
- Posted Svar: 5520 on Forum in Developers Visma.net. 24-10-2023 07:47
- Got a Kudo for Svar: 5520. 24-10-2023 07:47
- Posted Svar: 5520 on Forum in Developers Visma.net. 23-10-2023 11:36
- Kudoed 5520 for andreasaulin. 23-10-2023 11:36
- Kudoed API specification is incomplete - where are the 404 return types? for ReinderReinders. 22-05-2023 16:51
- Posted Svar: Error message "Invalid token" on Forum in Developers Visma.net. 05-05-2023 13:32
- Posted Re: Urgent - Connection to cache service failed on Forum in Developers Visma.net. 27-03-2023 20:34
- Posted Svar: Issues for end users with the new Visma Connect Authentication and tenant-id in App Store on Forum in Developers Visma.net. 20-02-2023 13:36
- Posted Svar: Issues for end users with the new Visma Connect Authentication and tenant-id in App Store on Forum in Developers Visma.net. 13-02-2023 10:03
Useful pages
Contact us
Copyright © 2022 Visma.com. All rights reserved.
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America