My Products
Help

[Release Notes] - Visma.Net API 10.04.0 - 11-06-2024

by Sandra Anté (Updated ‎14-06-2024 08:46 by Sandra Anté VISMA )

 

API - Due dates for breaking changes

Release Notes

Documentation

Due

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.

May 1, 2024

Planned removal of VNI authentication method

We are extending the deadline for phasing out VNI authentication method from December 31st 2023 til latest June 1st 2024.

ISVs should register their (existing) integrations in the Developer Portal and use Connect authentication instead before the stated end date.

Benefits of this change:

- One preferred method of authentication across Visma.net ERP portfolio

- Better security using scopes

- Let customer be more in control (customer grants access explicitly)


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



Jun 01, 2024

Planned removal of Sales Order API endpoints



We plan to be functionally complete by Q3-2024 (30th of September 2024), thus new due date being end of Q4-2024(31st of December 2024). 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...


Swagger for Visma.net.ERP.SalesOrder.API

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




Dec 31, 2024