About adrianm

Oskar Jansson · ‎24-04-2025

Hi @adrianm, “What return code for timeout will be?” 504 Gateway Timeout. “If the timeout happens on PUT/POST, will the operation also be cancelled?” This depends on the business logic behind the endpoint. If there is no actual checking there - within the transaction or process - that the client still is connected, then the transaction should go through, even though the client got a timeout response. “OpenApi and versions” "v1" as version has been the same always and will probably still be for a while. It can be looked upon as the version of the ERP API, not to be confused with the v1 or v2 in the url, which points to a particular endpoint version, or the OpenAPI specification version which is the version of the (swagger) specification format. Please let us know if you have any further questions. Hi @thingsio , “I assume this will not change the token request URL too?” You are correct, the URL for the request token will stay the same.(https://connect.visma.com/connect/token) Hi @jacob, “https://salesorder.visma.net/api/v3/ Wil this also move to https://finance.visma.net/ ?” The URL for Visma Net SalesOrder API will remain the same.(https://salesorder.visma.net/api/v3/)

adrianm · ‎07-04-2025

It is now 3 weeks until the webhook subscription moves to the portal. Is there a migration guide? Tried a few things in the portal but got confused. 1. The salesorder webhook has moved from financials to sales order but where do I find the other webhooks? 2. Earlier there was only one salesorder webhook (status change or custom action) but now there are 4 (create/delete/update/custom action). 2a. How does the automatic migration know which one to set up. 2b. Will the new "update" webhook trigger on all changes or just status changes? 3. When registering a webhook in the portal, the uri can't contain url-parameter (i.e. ?param=). We currently use a parameter for authentication. What will happen on migration? 4. The portal says I can register for one tenant only but there are no tenants available in "select tenant" list. 5. What url will be included in the webhook payload integration.visma.net or api.finance.visma.net? 6. We have webhooks that were registred with the old authentication. How can I see these? The subscription endpoint doesn't show these (probably because it is connected to the user).

adrianm · ‎14-03-2025

On supplier invoices from EFH system there is sometimes a need to adjust the vat amount. Visma.Net will not automatically recalculate the "expense amount" when the "deductable vat rate" is not 100%. TaxDetailUpdateDto need "expenseAmount" "taxDetailLines": [ { "taxId": { "value": "string" }, "taxableAmount": { "value": 0 }, "vatAmount": { "value": 0 } } ]

Yıldırım · ‎07-03-2025

Hello, it is required in the neXtgen Sales Order Service; however, it has only recently been implemented in the VismaNet ERP API and is currently optional. At this time, there are no plans to make it mandatory for requests. Additional information can be found on Using "ETag" and the "If-Match" conditional header in VismaNet API Endpoints

adrianm · ‎25-02-2025

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.

Joni Wolff · ‎18-02-2025

In v3 you can use GET /api/v3/SalesOrders/{type}/{orderId}/shipment

adrianm · ‎31-01-2025

I have PUT calls returning bad request when a product is not found. I was expecting 404 Not Found PUT: https://integration.visma.net/API/controller/api/v1/inventory/15392 { ... } Response: 400 Bad Request {"message":"Document not found : 15392"} This is another call to the same company a couple of months ago. PUT: https://integration.visma.net/API/controller/api/v1/inventory/000121 {...} Response: 404 Not Found {"message":"Inventory with number 000121 could not be found"}

Oskar Jansson · ‎21-01-2025

It was released today at 13:30

adrianm · ‎21-01-2025

A client has 50000 customers in Visma.Net. When searching for a specific attribute it works sometimes, taking a minute or two but often fails with "An existing connection was forcibly closed by the remote host.". This happens after 5-10 minutes so I assume it is some kind of internal timeout between the API and Visma.Net. (My timeout is 1 hour). Is there anything I can do? I don't mind waiting a long time for the result. Search Url looks like: https://integration.visma.net/API/controller/api/v1/customer?attributes={"CUST03"%3A"28"}

JoLu · ‎03-01-2025

You can only use the service flow for an existing customer with a tennantID, I don't know how you create a customer using the API since we don't do that, you will need to ask Visma about that.

carl_maddenanalytics · ‎12-12-2024

Is there any news regarding this? I am having the same issue and need to set destination warehouse when creating a transfer order. Any workarounds? Thankful for any pointers!

Oskar Jansson · ‎28-11-2024

I can now confirm that the size limit for attachments is the same in both the API and the UI.

adrianm · ‎04-11-2024

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

adrianm · ‎04-11-2024

> 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.

adrianm · ‎09-09-2024

Kind of a strange problem. We create invoices from orders like: * POST api/v3/salesorders * POST controller/api/v2/salesorderbasic/{orderType}/{orderNumber}/action/prepareInvoice * POST controller/api/v1/customerinvoice/{invoiceNumber}/action/release this works fine but for not for credit invoices * POST api/v3/salesorders * POST controller/api/v2/salesorderbasic/{orderType}/{orderNumber}/action/prepareInvoice * POST controller/api/v1/customerCreditNote/{creditNoteNumber}/action/release The credit invoice is not released, no error message, but can be released in the GUI. Also, a credit invoice created directly, i.e. not from order, can be released via API. What can we do differently to work around this?

Marten Voort · ‎04-09-2024

I have just done some testing, for the entity customers there is no noticeable delay, so there is no need to add a delay for this.

Sander_Feenstra · ‎19-06-2024

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

adrianm · ‎20-03-2024

Application types using the end-user credentials, e.g. native, does not have/need to add your app from the store (so no invitation code is necessary). Documentation could be more clear about this. Only requirement is the user has the "API User" role and your app will get access. Note that the authentication/token will still succeed if user lacks the "API User" role but you will get a strange error when trying to access the API.

Suzdar Ibrahim · ‎22-01-2024

Great! Thanks for the feedback. Will let the team know 😀.

adrianm · ‎15-01-2024

That message is the default message the API returns when something in the backend crashes. It has nothing to do with concurrency or timing. It might be temporary and a retry will work but it could also be your request having an invalid value.

Yıldırım · ‎15-12-2023

Thanks for sharing, Adrian ! To my knowledge, to be able to get tenant_ID via JWT and UserInfo you need to adjust the following settings. 1) Developer Portal 2) Adding OpenID Identity scope : tenants to your token request e.g. openid email profile tenants vismanet_erp_interactive_api:create vismanet_erp_interactive_api:read vismanet_erp_interactive_api:update vismanet_erp_interactive_api:delete

David Tandberg-Johansen · ‎22-11-2023

Hi, Has Visma verified that all the endpints at integration.visma.net/API/controller/api/(V1/V2) work with Tenant based Authentication? If not all works with Tenant based Authentication, does it exists a list of which doenst support it?

Svar: Important: End of VNI and transition to Azur...

Status of webhook change

Add expense amount to TaxDetailUpdateDto

Re: If-match required?

Re: Migrering fra .NET Framework (System.ServiceMo...

Re: Get shipments for order

Inventory endpoint returns bad request on not foun...

Re: Inventory GetAll only returns active

Searching for attribute often fails

Svar: Issues for end users with the new Visma Conn...

Re: Creating Transfer orders

Re: Is there a size limit on attachments via API?

Re: prepare invoice does not return error message

Re: How can I create a customer without an email a...

Can't release credit order created from order via ...

Re: Delay between Visma Net API and Sales Order Ap...

Re: Getting access_token returns invalid_grant aft...

Re: Issue with Invitation Code

Re: Scope in native app authentication

Re: Error: Another process has added 'SOOrder'

Re: Question on native app authentication

Sv: Subscription endpoint does not work with tenan...

Useful pages

About Visma

Contact us

Follow us