My Products
Help

[Release Notes] - Visma.Net API 10.05.0 - 18-06-2024

by Rozhat (Updated ‎01-07-2024 11:21 by Magnus Johnsen VISMA )

Release Notes

Documentation

Default expand toggle 

values in GET 

KitAssembly endpoint 

to be set to FALSE 

instead of TRUE







Expand toggle values that are currently set to TRUE by default will be changed to FALSE by default.

New endpoint - GET 

SupplierAccount






Endpoint provides the possibility for integrations to fetch GL accounts based on the configuration 

SupplierID (Mandatory String for URL path) 

vatRegistrationId (Parameter) used to determine what location to pick the value from. In the response content the 

AccountID matching the result from this Supplier will be given under the SupplierAccount. 

linesNonTaxable (Parameter) By default set to false. Expense account will be picked matching the class type from 

the supplier. With the “Domestic” class type this parameter can be used to give in the response “Expense non-

taxable account” instead of the “Expense account”. 

supplierItemId (Parameter) Will verify if there is a match from this “Vendor Inventory ID” within the Inventory ID’s. 

Value is linked to the Item in the Vendor Details -tab in the field “Vendor Inventory ID”. If Item ID is found 

corresponding to the Vendor Inventory ID for the Supplier the GL Account match from the configuration will be given 

into response under SupplierItemAccounts. If there was a match, the matched ItemID and AccountID will be shared 

in the response content together with the SupplierItemId it was fetched with. Multiple supplierItemId:s can be fetched 

during the same call

New field in the 

customer invoice 

endpoints

A new field "Revoked" that can be used by the third party integrators is available now in the following endpoints: 

- GET /api/v1/customerinvoice/{invoiceNumber} 

- GET /api/v1/customerinvoice 

- PUT/api/v1/customerinvoice/{invoiceNumber} 

- POST/api/v2/customerinvoice

Supplier Ledger GET 

endpoints - Removed 

empty spacing from 

Vendor ID field when 

retrieved and length 

had been changed

If the Vendors Segment ID length value was increased and in the system there were existing vendors with lower 

character lengths. This resulted in the response including empty spacing for the supplier number to match the current 

length of the segment. This has now been fixed

 

 

API - Due dates for breaking changes

Release Notes

Documentation

Due

Planned removal of VNI authentication method

As mentioned many times earlier, VNI authentication method had its End of life on 1st of June 2024. 

This is an urgent notice for all ISVs and partners with integrations in Visma.net: 

We have previously informed all partners and ISVs to migrate their existing integrations to Visma.net using the new authentication 

method through Connect. 

As from June 1st deadline is reached it is important to know that starting from the deadline, we will initiate throttling of these 

integrations. This means that we will start limiting the number of calls per hour per integration. During June we will gradually 

decrease the limit and allow less calls per hour. 

Additionally, starting mid-June, we will cease to issue new access tokens for these integrations. 

More information for ISVs on how to migrate existing integrations and\or setup new integrations can be found in the international 

developer community: 

https://community.visma.com/t5/News-in-Developers-Visma-net/Visma-net-ERP-APIs-are-now-available-for...

/542148



Jun 01, 2024

Planned removal of Sales Order API endpoints



We plan to be functionally complete by Q4-2024 (31st of December 2024), thus new due date being end of Q1-2025(31st of 

March 2025). If any change would occur for this, we will announce that as soon as possible, 

A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. 

The following API endpoints will be removed: 

GET /controller/api/v1/salesorder/{orderNbr} 

GET /controller/api/v1/salesorder/{orderType}/{orderNbr} 

GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut 

GET /controller/api/v1/salesorder 

GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions 

POST /controller/api/v1/salesorder 

POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder 

POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder 

PUT /controller/api/v1/salesorder/{orderNbr} 

GET /controller/api/v1/salesorderbasic/{orderNbr} 

GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} 

GET /controller/api/v1/salesorderbasic 

POST /controller/api/v1/salesorderbasic 

PUT /controller/api/v1/salesorderbasic/{orderNbr} 

POST /controller/api/v2/salesorderbasic 

POST /controller/api/v2/salesorder 

POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder 

POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder 

All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list 

of affected endpoints will also be extended, so pay attention to future updates. 

For more information on how to use the Visma.net ERP Sales Order Service, please visit: 

https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-s...

 p/401436

Swagger for Visma.net.ERP.SalesOrder.API 

https://salesorder.visma.net/swagger/index.html





Mar 31,  2024