Visma.net ERP NeXtGen Sales Order API v3: New PATCH and POST endpoints now available

[#1]

We are really excited to announce that we have now released the new and highly requested endpoints PATCH and POST in the Visma.net Sales Order API v3.

We are looking forward to your input and feedback.

PATCH

Create modifications/updates to an existing sales order:

PATCH/api/v3/SalesOrders/{type}/{orderId}

Create modifications/updates to an existing sales order line:

PATCH/api/v3/SalesOrders/{type}/{orderId}/lines 

POST

Add new line(s) to an existing sales order:

POST/api/v3/SalesOrders/{type}/{orderId}/lines

Authentication

Please note that it is possible to authenticate “old” api integrations with Visma Connect. Since Sales Order API v3 only supports authentication via Visma Connect, this will make it easier to use resources/endpoints from both APIs. 

For example, you want to know which inventory items you can add to a sales order, because you are using the same authentication you can easily get the Inventory information from the "old" api integration.

For more information about Visma Connect authentication, please read:

https://community.visma.com/t5/Knowledge-base-in-Developers/Guide-Move-from-VNI-to-Visma-Connect-Aut...

Getting  started

How to get started with the Sales Order API v3, plus additional information, please see:

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

[Yıldırım]

Great news !

[SvenTore]

This is currently not a good replacement for V1 /V2. Looking at the swagger documentation the PATCH for sales order is missing missing orderLines array. It's really important to be able to post changes to an order atomically, as with a create POST, where lines are included with the order.

[Joni Wolff]

Hi

" It's really important to be able to post changes to an order atomically, as with a create POST, where lines are included with the order."

Could you elaborate why it is important to be able to change both header and lines in the same operation?

[SvenTore]

When the user is "saving" it's expected to have success or failure. 

If I'm adding two lines, changing one and deleting one + setting a field to trigger something on the order head I expect it to either complete or fail completely, and be able to retry the request