About johanpettersson

johanpettersson · ‎05-01-2022

When requesting a range of data items (customers etc.) using pagination, does the "SameRequestLimit" take the requested page into consideration? When trying this out in the swagger ui, we get error 429 (SameRequestLimit) when requesting more than five different pages within one minute. Is that the intended behaviour?

johanpettersson · ‎08-12-2021

I can confirm that we also get the above errors in large numbers. Last night we started exporting 70000 invoices to Visma through the API, and between 01:00 and 02:45 tonight almost all of the export attempts during that time failed due to the above errors. After 02:45 things have gotten better but we still get random timeouts.

johanpettersson · ‎01-12-2021

I've sent an email to developersupport. Thanks for your help!

johanpettersson · ‎01-12-2021

Do you have any idea why the release operations fail in Visma? Is there anything we can do on our end to prevent this? The night between monday and tuesday we exported 18000 invoices to the api, and 8000 of them never got released in Visma even though the release operation got a 200 status code on all of them. A 45% fail rate in Visma is not that great and there must be a way to investigate why this happen and what we can do to avoid it.

johanpettersson · ‎30-11-2021

Also, I don't know if this is just a coincidence, but we started seing this behaviour with failed release the last few days, after we also started creating attachments for all the invoices. So we: - Save the invoice - Create the attachment for the invoice (same attachment file for all invoices) - Release the invoice All the steps succeed without errors, but som invoices never get released. Edit: Also, we handle invoices in parallell. We always perform the steps above in the order described for the same invoice, but we send calls for different invoices in parallel. This shouldn't be a problem, right? We comply to the rate limits att all time, maximum calls/h, max concurrent calls and so on, and we never get any error codes of any kind.

johanpettersson · ‎30-11-2021

We currently have no retry logic for invoices that get no error from the api, and we really shouldn't need that I guess. If the job is queued in Visma without errors we expect the job to get executed unless there is something wrong with the invoice (but in that case we would expect the api to not queue the job and not return 200). Since these "failed" invoices can be released without any problem later on in both the api and the UI we expect them to actually be released a some point in time, if we get code 200.

johanpettersson · ‎30-11-2021

We are saving customer invoices and creating attachments for them in large batches, but we are seeing intermittent errors when creatig the attachments, with response code 500 from the API. The attachments we are creating for the invoices always have the same content and file name, so there is no difference for the ones succeeding and failing. Examples of message returned when we get error code 500: {"message":"VismaId: ff6b674c-8647-4e00-b190-afb0dc4c2f45. Safe handle has been closed"} {"message":"VismaId: fa7417f2-3741-4593-9af3-878c942eeb3d. One or more errors occurred."} {"message":"VismaId: 021077a8-b14a-4b47-aece-fef5d2014da2. Could not save the attachment"} {"message":"VismaId: 05c2923c-64a3-4da2-beeb-188cdabea513. Could not save the attachment"}

johanpettersson · ‎30-11-2021

We are creating and releasing invoices through the api in large batches, but some of the invoices are not being released even though the api returns no error. The procedure for each invoice is: - Save the invoice - Create an attachment - Release the invoice The api returns no errors for any of these calls, but a large number of invoices still are not released 12h later. The invoices that hasn't been released can be relased manually in Visma.net Financials.

johanpettersson · ‎02-11-2021

It seems like it is not possible to create/update UnitOfMeasure through the Visma.net api, is this correct? Sorry if I'm asking a question with an obvious answer, but I was a bit surprised to discover this in the api.

johanpettersson · ‎27-10-2021

Hi, We are developing an integration for Visma.net and have some questions regarding the api client (client id) and the redirect uri. Our product is not a centralized system, we have separate system installations for each customer (some on premise, some hosted by us). Do you have any best practices in these scenarios, regarding the api client and redirect uri? The authorization flow uses a redirect uri, which will vary in this case. - Should we use a separate api client for each customer integration? - Should we use a single api client and allow multiple redirect uri:s for the api client? - Should we use a single api client and specify a single central redirect uri and route our authorization requests to/from this uri? We would really like your feedback regarding this use case.

Pagination and SameRequestLimit

Svar: Reoccurring error messages from the API even...

Re: Customer invoices not being released

Re: Customer invoices not being released

Svar: Customer invoices not being released

Svar: Customer invoices not being released

Intermittent error when creating invoice attachmen...

Customer invoices not being released

Create UnitOfMeasure

Single or multiple api clients/redirect uri:s

Useful pages

About Visma

Contact us

Follow us