[Release Notes] - Visma.Net API 10.32.0

[#1]

Release Notes	Documentation
New parameters included into supplier domains GET endpoints	New parameters now available in the following endpoints: GET/controller/api/v1/supplierInvoice GET/controller/api/v1/supplierPayment GET/controller/api/v1/supplierdocument GET/controller/api/v1/supplier/{supplierNumber}/invoice GET/controller/api/v1/supplier/{supplierNumber}/document The new parameters which are now available: - paymentType (added for SupplierPayment) - Status (added for SupplierPayment) - Supplier (Added for SupplierInvoice & SupplierDocument) - Item (Added for all except SupplierPayment) - branch (Added for all) - financialPeriod (Added for all) - dueDate & dueDateCondition (Added for all) - docDate & docDateCondition (Added for all) - balance & balanceCondition (Added for all)
Resolved: Incomplete GET Inventory API Response	The Inventory API endpoint /controller/api/v1/Inventory previously returned only active items when no status parameter was specified. This has been resolved, and now all items, regardless of status, are returned as expected.
Some API endpoints allow non-ascii characters in the LotSerialNbr field	Previously, non-ascii characters were allowed in the lot-serial number field in the payload for POST/PUT purchaseReceipt- , POST/PUT salesOrder- and POST/PUT Shipment-endpoints. This has now been fixed

API - Due dates for breaking changes

Planned removal of Sales Order API endpoints

We plan to be functionally complete by Q1-2025 (31st of March 2025), end of life date for the endpoints will be announced in February 2025. 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 might 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

Sept 30, 2025