That is not the only change: 1. timestamp is now a string, not a number 2. resourceUri can no longer be used to fetch the resource   (visma migrated webhooks to a new platform this morning. The migration was announced a long time ago but the actual date has not been published. It was supposed to be transparent except IP-adresses) ... View more

Can I get a response to this?   2. What return code will we get on timeout? 3. If the timeout happens on PUT/POST, will the operation also be cancelled? (i.e. if an order with many rows times out, will the order be created or not?)   Also noted the url to the OpenAPI file has changed. Can someone officially state something about the status of the new url? When will it be ready for production use? Does it have its own versioning (still says v1 in OpenApi specification)? ... View more

@HansK2, sorry, I just meant that the new swagger reflects how the API actually works. I understand it is a change that can introduce breaking changes in auto-generated clients and it should probably have been mentioned by Visma.   Havn't used nswag to generate clients but isn't there a settings to make optional properties nullable? As you say, if it is not nullable there is no way to know if a property was included or not and that can't just be a problem with visma.net api? ... View more

@HansK2, I think Visma.Net uses "JsonIgnoreCondition.WhenWritingNull" so properties are never null in responses, they are ignored. i.e. undefined in js-terminology.   In OpenApi, all properties are optional unless marked required. (unfortunately Visma.Net often has the text "Mandatory" in the description instead of using required)   The new swagger is also correct.     ... View more

>Does "available" mean it is ready for production use? > i.e. is it monitored and covered in the status page etc?   Answering this myself and it is "No, not ready for production".   One of the first tests was to create a supplier invoice. The location returned was: http://finance.visma.net/1038011008/api/v1/supplierInvoice/Invoice/200120   which doesn't work to fetch the invoice. POST: https://api.finance.visma.net/v1/supplierInvoice Headers: { Accept: application/json Authorization: <hidden> Transfer-Encoding: chunked Accept-Encoding: gzip Accept-Encoding: deflate Content-Type: application/json; charset=utf-8 } {"documentType":{"value":"Invoice"},"origInvoiceDate":{"value":"2025-03-11T00:00:00+01:00"},"supplierReference":{"value":"ABC123xxx"},"supplierNumber":{"value":"50013"},"currencyId":{"value":"SEK"},"dueDate":{"value":"2025-04-10T00:00:00+02:00"},"invoiceLines":[{"operation":"Insert","transactionDescription":{"value":"Kost"},"costInCurrency":{"value":9722.36},"accountNumber":{"value":"2446"}}]} Response: 201 Created Headers: { Cache-Control: no-cache Pragma: no-cache ETag: "AAAAAB1sBKE=" Location: http://finance.visma.net/1038011008/api/v1/supplierInvoice/Invoice/200120 X-Handled-By: Visma-PX.Export/AuthenticationManagerModule Set-Cookie: <crumbs>; expires=Mon, 10-Mar-2025 11:33:11 GMT; path=/; HttpOnly Set-Cookie: <crumbs>; path=/; HttpOnly Set-Cookie: <crumbs>; path=/; HttpOnly Set-Cookie: <crumbs>; path=/; HttpOnly VnfInstanceId: ERP_SE_DEMO_0005 Request-Context: appId=cid-v1:898a32d3-12b9-4a24-865d-6ed5d67429a6 Access-Control-Expose-Headers: Request-Context Referrer-Policy: origin-when-cross-origin Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: application/json X-XSS-Protection: 1;mode=block x-ms-request-id: 402cbb15-12ee-4171-b4d1-7ed83526a14b Date: Tue, 11 Mar 2025 11:33:14 GMT Content-Length: 0 Expires: -1 }   ... View more

Does "available" mean it is ready for production use? i.e. is it monitored and covered in the status page etc?   Also, how does versioning work with the new url. Swagger just says "v1"   ... View more

Jag har bara använt dotnetcore för alla mina VBSintegrationer sen 2019 och de fungerar fint.   På den tiden var lite klurigt att få det att fungera men jag använder samma kod idag så vet inte om det är lättare nu. 1. Du måste använda "System.ServiceModel.Http" version 4.10.3 eller tidigare. Version 8 ger något kompileringsfel som jag inte brytt mig om att undersöka närmare 2. Du måste göra konfigurationen i kod, inte i .config 3. DotNetCore tillåter inte att man skickar lösenord över http vilket VBS gör. Det innebär att den enda metod som ingår i standardinstallationen av VBS, WsHttpBinding, inte kan användas. Använd Anonymous eller https. 4. Visma.BusinessServices.Client refererar till ett par klasser som inte finns i .Net (i alla fall inte 2019). De används inte men bara referensen gör att man inte kan anropa `RequestBuilder.Dispatch` utan är tvungen att anropa den privata metoden `RequestBuilder.DispatchInternal` med reflection.     ... View more

1. Doesn't the API already have a timeout? e.g. https://community.visma.com/t5/Forum-in-Developers-Visma-net/Searching-for-attribute-often-fails/td-p/707481   2. What return code will we get on timeout?   3. If the timeout happens on PUT/POST, will the operation also be cancelled? (i.e. if an order with many rows times out, will the order be created or not?)   ... View more

@Oskar Jansson wrote: Hi, you need to do separate GET request for each status needed. With the current implementation, only one status can be specified per GET request. I don't understand. Does this mean this not documented breaking change in the endpoint is permanent?   What happened to a solution for the issue where the Status parameter defaults to Active is on its way. ... View more

Thank you for the quick response. ... View more

Update, imported ~400 smaller attachments which worked but with many Internal Server Error (500).   Most common (~20): {"ExceptionType":"java.util.concurrent.TimeoutException","ExceptionMessage":"IO Exception while copyingStreams: java.util.concurrent.TimeoutException","ExceptionFaultCode":"5520","ExceptionMessageID":"5520_f22a8e1a-1fa4-4507-b5f1-69ef3b8c0abc","ExceptionDetails":""}   But also a few {"ExceptionType":"java.net.SocketException","ExceptionMessage":"Error occured while connecting to the service when trying to get response code (IOException)","ExceptionFaultCode":"5521","ExceptionMessageID":"5521_e8c21ad6-b84c-436f-b24d-f5dfc67a2d6f","ExceptionDetails":""}   and   {"message":"VismaId: 6e79f0dd-aa24-49d8-b096-39c91a3acfb4. A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)"}   I have used the same code earlier to import thousands of attachments on supplier invoices without problems. Has the implementation of attachments in the api changed (like now using java :-)) ... View more

Yes, i know that but it doesn't scale. ... View more

> Is there any way to create specific customers without email addresses without having to disable dunning letters in the customer class?   No, you can't. The issue has been open for over 4 years.   ... View more

Since v3 is not complete I haven't converted any existing integrations yet.   But the procedure is usually * Fetch customer * CreateCustomer when not found * CreateOrder   So if the delay is more than the API roundtrip time I need to know how much delay to add. ... View more

Thank you for your quick reply.   Is fixing this part of the "All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed."?   New subaccount is probably a rare thing but creating customers at the same time as an order is a common scenario. ... View more

> This will let you authenticate using client_credentials with a tenant id instead. Only works if you can store the secret securely. Otherwise you need to create one service application for each tenant. ... View more