Release Notes Documentation Improved performance of POST v1/purchaseorder The POST v1/purchaseorder endpoint is now up to 1,6 times faster than before.  New endpoint v2/salesorder/[orderType]/[orderNumber]/action/sendbymail  The new endpoint v2/salesorder/[orderType]/[orderNumber]/action/sendbymail initiates the process of sending an order by email.     API - Due dates for breaking changes Release Notes Documentation Due 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 Q2-2024 (30th of June 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   ... View more

Dear Developer, Throughout the years, our API's for Visma.net ERP have expanded greatly both in scope and use. Our centralized development team has been happy to support you, but we think we can do better. Using localized resources with knowledge of the local customers and markets, we will be able to give more specialized Support in local languages. Starting February 1st 2024, the email address developersupport@visma.com will therefore be deprecated. The developer forum will still be the place to discuss or ask for help from other ISV's or our API support. We will keep publishing News and Knowledge there, and the Ideas section will remain the place to post your wishes for improvement. If you need one-to-one support, you can contact us via Service Cloud tickets using the following portal:     Country Partner portal Support email Norway  & Denmark https://visma-swno.my.site.com/s/api cloud.api.support@visma.com Sweden - api.consulting.se@visma.com  Netherlands https://visma-software-nl. force.com/supportportal/s/ - Finland - sovellustuki@visma.com Please use this system when you need to contact Visma directly for API Support, for example when this involves sensitive customer data or if you encounter database specific issues. We trust our cooperation will only strengthen with this change and look forward to supporting you through our local support teams from now on. ... View more

Scheduled maintenance for Visma.net ERP to optimize SQL environment Scheduled for  Feb  4 ,  01:00  -  05:00  CET Update: Correct date and time is Feb 7, 2024 01:00-04:30 CET We will do Right Sizing on our SQL environment. Visma.net ERP UI and API will be unavailable during this time.   https://status.visma.com/incidents/3pr219b5rlb7 ... View more

Release Notes. Documentation New field "consolidateInvoices" available on the Customer endpoints A new field "consolidateInvoices" is now available on the following endpoints' response message: -GET/controller/api/v1/customer/{customerCd} -GET/controller/api/v1/customer -POST/controller/api/v1/customer -PUT/controller/api/v1/customer/internal/{internalID} -PUT/controller/api/v1/customer/{customerCd} This shows if the customer has the Consolidate invoices check box selected in the Customers (AR303000) window. The API documentation will be updated after the pilot phase is done. New section "parentRecord" available on the Salesorder GET operation  A new section "parentRecord" is now available on the following endpoints' response message: -GET/controller/api/v1/salesorder -GET/controller/api/v1/salesorder/{orderNbr} -GET/controller/api/v2/salesorder -GET/controller/api/v2/salesorder/{orderNbr} This shows the details of the parent customer to which the invoice has been sent from the child customer. Location endpoint now returns 400 instead of 500 error when request has incorrect data Earlier, Location endpoints returned a 500 internal server error for requests containing an invalid postcode or an incorrect business account. This has now been corrected so that a 400 bad request error will be returned in these situations.   API - Due dates for breaking changes Release Notes Documentation Due 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 Q2-2024 (30th of June 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 ... View more

Release Notes Documentation New section "childRecord" available on the CustomerInvoice GET operation A new section "childRecord" is now available on the following endpoints' response message: -GET/controller/api/v1/customerinvoice -GET/controller/api/v1/customerinvoice/{invoiceNumber} This shows the details of the child customer for which the invoice has been sent to the parent customer. Improved performance on GET SupplierInvoice endpoint The performance of the GET SupplierInvoice endpoints has been improved. The new endpoint will be tested by a small number of clients in the beginning. Once the pilot testing phase is completed, the improvement will be enabled for everyone. Extra validation and additional improvement to the PUT TimeCard endpoint The PUT TimeCard endpoint now has an extra validation when neither Summary nor Materials have been added to the payload. The following error message "Update payload should contain at least a Summary or Materials." will be displayed. Credit note now subtracted from invoice when creating customer payment via API Earlier, when creating a customer payment with an invoice and a credit note using the CustomerPayment API endpoint, the credit note was not subtracted from the invoice. This has now been fixed.   API - Due dates for breaking changes Release Notes. Documentation Due 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 Q2-2024 (30th of June 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     ... View more