Important update on Sales Order API Changes The previously communicated end-of-life date for the old SalesOrder V1 and V2 endpoints has been postponed. This decision was made after receiving input from several ISVs and considering the many other changes we are bringing related to the end of VNI.  As we transition to the next generation of our APIs, some of our old SalesOrder V1 and V2 endpoints will be deprecated during 2025.   We understand you're eager for a concrete end-of-life date for the V1/V2 SalesOrder endpoints, but we cannot provide one yet. Rest assured, we will provide at least a six-month notice ahead of the actual end-of-life date.   However, we highly recommend initiating the transition to the V3 API as soon as possible. By starting early, you'll not only be ahead of the curve but also gain the advantage of ample time for testing and ensure a seamless integration before the deadline. This will give you flexibility and time to thoroughly test your integrations with the V3 API, helping to guarantee a smooth cutover when the time comes.   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 integration, this can be a time-consuming process with necessary testing to confirm that your integration is working as expected.   What remains to be done before v3 covers the v1/v2 functionality? The v3 endpoints are planned to cover the functionality of the Sales Order v1/v2 endpoints (see list below), by March 2025. Follow our release notes for updates on this matter.   The only functionality that is still under development is the LOT/Serial and expiration date functionality.   What should you do next?   Identify: Determine if your Visma Net Integrations utilize any of the V1/V2 endpoints listed below. Plan: If you are using the affected endpoints, start planning your project to migrate to the V3 endpoints. Contact: If you are a Visma Net customer, contact your partner or integration vendor to clarify the necessary steps for your specific instance.     What are the changes? The following API endpoints are scheduled for removal:   Method Endpoint Status GET /controller/api/v1/salesorder/{orderNbr} To be removed GET /controller/api/v1/salesorder/{orderType}/{orderNbr} To be removed GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut To be removed GET /controller/api/v1/salesorder To be removed GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions To be removed POST /controller/api/v1/salesorder To be removed POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder To be removed POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder To be removed PUT /controller/api/v1/salesorder/{orderNbr} To be removed GET /controller/api/v1/salesorderbasic/{orderNbr} To be removed GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} To be removed GET /controller/api/v1/salesorderbasic To be removed POST /controller/api/v1/salesorderbasic To be removed PUT /controller/api/v1/salesorderbasic/{orderNbr} To be removed POST /controller/api/v2/salesorderbasic To be removed POST /controller/api/v2/salesorder To be removed POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder To be removed POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder To be removed   All necessary features will be integrated into the new Sales Order Service API before the transition date. We are committed to ensuring a smooth transition and will provide updates as they become available. ... Meer weergeven

Release Notes Documentation Align behaviour of v1 and v2  createShipment endpoint with UI Improved quality in v1 and v2 salesorder/[ordernumber]/action/createShipment endpoints  regarding salesorderstatus Implementation of   ETag/If-Match function ality in the supplier endpoints In supplier endpoints the ETag/If-Match functionality is now implemented.  ETag and If-Match are HTTP headers that are used to prevent conflicts when multiple clients are  trying to update the same resource at the same time and avoid data inconsistency.  The main benefit is conflict prevention; by using If-Match headers, clients can prevent conflicts  when multiple clients are trying to update the same resource at the same time For further information, please see the following article:  Using "ETag" and the "If-Match" conditional header in VismaNet API Endpoints Implementation of   ETag/If-Match function ality in the shipment endpoints In shipment endpoints the ETag/If-Match functionality is now implemented.  ETag and If-Match are HTTP headers that are used to prevent conflicts when multiple clients are  trying to update the same resource at the same time and avoid data inconsistency.  The main benefit is conflict prevention; by using If-Match headers, clients can prevent conflicts  when multiple clients are trying to update the same resource at the same time Implementation of   ETag/ifMatch functionality in the purchaseReceipt endpoint In purchaseReceipt endpoints the ETag/If-Match functionality is now implemented.  ETag and If-Match are HTTP headers that are used to prevent conflicts when multiple clients are  trying to update the same resource at the same time and avoid data inconsistency.  The main benefit is conflict prevention; by using If-Match headers, clients can prevent conflicts  when multiple clients are trying to update the same resource at the same time Implementation of   ETag/If-Match function ality in the purchaseOrder endpoints In purchaseOrder endpoints the ETag/If-Match functionality is now implemented.  ETag and If-Match are HTTP headers that are used to prevent conflicts when multiple clients are  trying to update the same resource at the same time and avoid data inconsistency.  The main benefit is conflict prevention; by using If-Match headers, clients can prevent conflicts  when multiple clients are trying to update the same resource at the same time     API - Due dates for breaking changes Release Notes Documentation Due 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  at a later point.  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-service-Visma-net-  ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API  https://salesorder.visma.net/swagger/index.html   ... Meer weergeven

Release Notes Documentation Introduce new custom fields in purchaseOrder- endpoints Introduce new custom fields for purchaseOrder- and purchaseOrderBasic -endpoints  (header and lines):  - CustomStr1  - CustomStr2  - CustomStr3  - CustomStr4  - CustomStr5  - CustomDec1  - CustomDec2  - CustomInt1  - CustomInt2  - CustomDateTimeUtc1  Valid for:  POST v1/purchaseOrder  PUT v1/purchaseOrder  GET v1/purchaseOrder?IncludeCustomFreeField  GET v1/purchaseOrder/[ordernumber]?IncludeCustomFreeField  POST v1/purchaseOrderBasic  PUT v1/purchaseOrderBasic  GET v1/purchaseOrderBasic?IncludeCustomFreeField  GET v1/purchaseOrderBasic/[ordernumber]?IncludeCustomFreeField Introduce new custom fields in shipment- endpoints Introduce new custom fields for shipment-endpoints (header and lines):  - CustomStr1  - CustomStr2  - CustomStr3  - CustomStr4  - CustomStr5  - CustomDec1  - CustomDec2  - CustomInt1  - CustomInt2  - CustomDateTimeUtc1  valid for:  GET v1/shipment[shipmentNbr]?IncludeCustomFreeFields=true  GET v1/shipment?IncludeCustomFreeFields  PUT v1/shipment[shipmentNbr]  POST v1/shipment Introduce new custom fields in  purchaseReceipt-endpoints Introduce new custom fields for purchasereceipt- and purchasereceiptBasic -endpoints  (header and lines):  - CustomStr1  - CustomStr2  - CustomStr3  - CustomStr4  - CustomStr5  - CustomDec1  - CustomDec2  - CustomInt1  - CustomInt2  - CustomDateTimeUtc1  Valid for:  POST v1/purchaseReceipt  PUT v1/purchaseReceipt  POST v1/purchaseOrderBasic  PUT v1/purchaseOrderBasic  GET v2/purchasereceipt?IncludeCustomFreeFields=true  GET v2/purchasereceipt/[receiptNbr]?IncludeCustomFreeFields=true  GET v1/PurchaseReceiptBasic?IncludeCustomFreeFields=true  GET v1/PurchaseReceiptBasic/[receiptNbr]?IncludeCustomFreeFields=true     API - Due dates for breaking changes Release Notes Documentation Due 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 the future.  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-service-Visma-net-  ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API  https://salesorder.visma.net/swagger/index.html Sept   30,  2025   ... Meer weergeven

Release Notes Documentation api/v1/dimension GET endpoints InternalId field  has been added For the GET endpoints regarding api/v1/dimension, InternalId field has now been added  and exposed into the responses. Improved performance on GET  SupplierPayment endpoint The performance of the GET SupplierPayment endpoints has been improved.     API - Due dates for breaking changes Release Notes Documentation Due 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-service-Visma-net-  ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Sept   30,  2025 ... Meer weergeven

As an API user I want to retrieve all items while allowing the ability to search by batch numbers and expiration dates. Currently, the API user has to manually search for batch numbers across all items. ... Meer weergeven

Release Notes Documentation Options to Send and Print Dunning Letters to the Customer API endpoint are now available Earlier, it was not possible to mark the boxes for sending and printing Dunning Letters to the Customer API endpoint in the Customer window. This has now been fixed. GET/SupplierDocument endpoint performance improvements The performance of the following GET endpoints has been improved:  - api/v1/supplierdocument  - api/v1/supplier/{supplierNumber}/document     API - Due dates for breaking changes Release Notes Documentation Due 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-service-Visma-net- ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API  https://salesorder.visma.net/swagger/index.html Mar  31,  2025 ... Meer weergeven

Release Notes Documentation PUT /v1/Supplierinvoice: Last line of the document deleted and new line inserted, “tstamp cannot be empty” -error Earlier, PUT /v1/Supplierinvoice gave an error “tstamp cannot be empty” if during the same update call last line of the document was deleted and a new line was being inserted using "addPOReceiptLines" or "addPurchaseOrders". 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-Visma-Connect/ba-p /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-service-Visma-net-ERP/ba-  p/401436 Swagger for Visma.net.ERP.SalesOrder.API  https://salesorder.visma.net/swagger/index.html Mar  31,  2025 ... Meer weergeven

Release Notes Documentation New field "Number of employees" on Supplier screen A new field "Number of employees" was added on screen AP303000.  This new field is also available in the GET, PUT and POST Supplier endpoints. Internal ID added to GET Supplier document  endpoint InternalID was added to all GET endpoints for controllers SupplierInvoice and  SupplierDocument in order to avoid full reload of the supplier document when the  supplier number is changed Creating purchase receipt with batch/expiry date  failed if the last line in receipt does not require batch /tracking info Earlier, POST purchasereceipt-endpoints with batch/expiry date was failing if the last  line in receipt did not require batch/tracking info. 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-Visma-Connect/ba-p /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-service-Visma-net-ERP/ba-  p/401436 Swagger for Visma.net.ERP.SalesOrder.API  https://salesorder.visma.net/swagger/index.html Mar  31,  2025 ... Meer weergeven

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-Visma-Connect/ba-p /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-service-Visma-net-ERP/ba-  p/401436 Swagger for Visma.net.ERP.SalesOrder.API  https://salesorder.visma.net/swagger/index.html Mar 31,  2024 ... Meer weergeven

Release Notes Documentation ProjectID and ProjectTaskID added to /api/v1/InventoryIssue API endpoint "ProjectID" and "ProjectTaskID" fields have been added to the POST v1/InventoryIssue API endpoint Populating the Branch field in the Project endpoint/GET requests Earlier, the Branch field was not populated in the Project endpoint/GET requests. This has now been fixed.  -GET/api/v1/project/{projectID}  -GET/api/v1/project/internal/{internalID}  -GET/api/v1/project  -GET /api/v1/project/tasks Endpoint POST api/v1/supplierinvoice/action/release now fully supports background-api operation Endpoint POST api/v1/supplierinvoice/action/release now fully supports background-api operation by specifying header erp-api-background on the request. Earlier, the operation was also started as a background operation, but wrongfully posted the webhook callback as soon as the operation started, whereas now it is posted on completion of the release process. Unit of measure (UOM) ignored in the Project transaction/POST request Earlier, the unit of measure (UOM) was ignored and defaulted to HOUR in the Project transaction endpoint/POST requests. This has now been fixed.     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-Visma-Connect/ba-p/542148 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-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Dec 31, 2024 ... Meer weergeven

Release Notes Documentation Improved performance on Discount and  Discount V2 endpoints for GET operation The performance on Discount and Discount V2 endpoints for GET operation has been improved.  This will be available for pilot customers first POST / PUT "LandedCost > Currency" via  Purchase Receipt Endpoint API POST / PUT "LandedCost > Currency" via  Purchase Receipt Endpoint API     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 planning to phase out VNI authentication method by the end of 2023. 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-Visma-Connect/ba-p/542148 Dec 31, 2023 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-  service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API  https://salesorder.visma.net/swagger/index.html Dec  31,  2024 Dec 31, 2024   ... Meer weergeven

Scheduled for  Mar  13 ,  01:00  -  04:30  CET   Maintenance window next week Tuesday-Wednesday night. We will be doing right sizing on our SQL environment. Visma.net ERP UI and API will be unavailable during this time.   This scheduled maintenance affects: Visma.net ERP (Visma.net ERP, Visma.net ERP API) and Visma.net ERP neXtGen Services (Visma.net ERP Sales Order Service, Visma.net ERP Payment Service, Visma.net ERP Sales Order Service UI, Visma.net ERP Journal Transaction Service, Visma.net ERP DataMart Service, Visma.net ERP Inventory Optimization Service). ... Meer weergeven

Release Notes Documentation Create/update customer via Customer endpoint with account and subaccount restrictions fixed Earlier, you could not create or update a customer via the Customer endpoint with account and subaccount restrictions. This has now been fixed for the following endpoints: - POST /api/v1/customer - PUT /api/v1/customer/{customerCd} - PUT /api/v1/customer/internal/{internalID} This will be released only for pilot customers at first. POST/PUT via Supplier endpoint not allowing certain combinations of account and subaccount to be used when restricted combination would be met during the call Earlier, you could not create or update a supplier via the Supplier endpoint with account and subaccount restrictions in place. The issue took place in a scenario where the account and subaccount starting values from the default supplier class would come across a restricted combination during the insert of new values. Error denied the call if a restricted combination was recognised, while updating the fields from the defaults to new values. This has now been fixed for the following endpoints: - POST /api/v1/Supplier - PUT /api/v1/Supplier/{supplierCd} This will be released only for pilot customers at first.     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 planning to phase out VNI authentication method by the end of 2023. 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-Visma-Connect/ba-p/542148 Dec 31, 2023 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-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Dec 31, 2024   ... Meer weergeven

Release Notes Documentation SupplierSubaccount now exposed in Supplier endpoint  You are now able to GET/POST/PUT the supplier ledger subaccount in the Supplier endpoint. The Supplier ledger sub field is available as supplierSubaccount. See the swagger documentation for more information. GET Supplier endpoint not displaying details on supplierPaymentMethodDetails correctly Earlier, there was a bug in GET Supplier endpoint in regards to supplierPaymentMethodDetails. This has now beens fixed and supplierPaymentMethodDetails are displayed based on paymentMethod.     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 Deprecated fields on Account endpoint Following fields are deprecated and will be removed on 20th of February 2024:  - ExternalCode1  - ExternalCode2  - AnalysisCode They should be replaced by fields: ExternalCode1Info, ExternalCode2Info, AnalisysCodeInfo, which contain more details. Feb 20, 2024 Planned removal of VNI authentication method We are planning to phase out VNI authentication method by the end of 2023. 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-Visma-Connect/ba-p/542148 Dec 31, 2023 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-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Dec 31, 2024   ... Meer weergeven

As an API user I want to be able to remove incorrect barcode references. As of today (version 9.80.0) I can only update a specific cross reference for a specific inventory. ... Meer weergeven

As an API user I want to be able to add extended cost to a sales order line. As of current version 9.78 I'm not able to add this through the API endpoints for salesOrder. This includes both v2 and v3 of the endpoint. This field is available through the UI and would help some of our internal integrations from OneStop ... Meer weergeven

As an API user I want to be able to add term start and end date to a sales order line. As of current version 9.78 I'm not able to add this through the API endpoints for salesOrder. This includes both v2 and v3 of the endpoint. This field is available through the UI and would help a few integrations that are reliant on this field. ... Meer weergeven