End of SalesOrder V1/V2 endpoints

What are the changes?

The following API endpoints are scheduled for removal:

MethodEndpoint
GET/v1/salesorder/{orderNbr}
GET/v1/salesorder/{orderType}/{orderNbr}
GET/v1/salesorder/{orderType}/{orderNbr}/rotrut
GET/v1/salesorder
GET/v1/salesorder/{orderType}/{orderNbr}/commissions
POST/v1/salesorder
POST/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder
POST/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder
PUT/v1/salesorder/{orderNbr}
GET/v1/salesorderbasic/{orderNbr}
GET/v1/salesorderbasic/{orderType}/{orderNbr}
GET/v1/salesorderbasic
POST/v1/salesorderbasic
PUT/v1/salesorderbasic/{orderNbr}
GET/v2/salesorder
POST/v2/salesorderbasic
POST/v2/salesorder
POST/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder
POST/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder
Tip

Watch our webinar regarding the change to SalesOrder V3 and our documentation for the SalesOrder V3 API

All necessary features have been integrated into the new Sales Order Service API.

Throttling of deprecated endpoints

To encourage final migration, we will begin throttling traffic to the deprecated V1/V2 endpoints starting April 1, 2026.

The deprecation and throttling process will follow these steps:

  • End of Life: March 31, 2026.
  • Throttling Begins: April 1, 2026. Requests to the deprecated endpoints will start to be rate-limited.
  • Gradual Reduction: The allowed traffic will be progressively reduced over time.
  • Final Shutdown: The deprecated endpoints will be permanently disabled in the future.
Note

More details about the rate limiting will be updated on our docs later this month.

Why is this happening?

To be able to meet the demand for more functionality as well as improved functionality in combination with the demand for higher throughput of transactions, we have to move from the Classic endpoints to NextGen endpoints. Our new SalesOrder V3 endpoint will offer improved functionality, increased security, and better performance. Put in other words, by retiring older endpoints, we can focus on delivering these enhancements without the constraints of maintaining outdated systems.

In summary, this change ensures that you will benefit from the latest technology and innovations we offer. It’s part of our goal to provide you with a more robust, efficient, and future-proof service.

How will this affect you?

This change will require you to rewrite integrations that use the affected V1/V2 endpoints. For most instances, this change should be quite manageable. But for more complicated integrations, this can be a time-consuming process with necessary testing to confirm that your integration is working as expected.

What should you do next?

Identify: Determine if your Visma Net integrations utilize any of the V1/V2 endpoints listed above.

Plan: If you are using the affected endpoints, migrate to the V3 endpoints.

Contact: If you need assistance identifying which clientId, tenantId, or endpoints are still using the deprecated API versions:

Last modified March 11, 2026