Did you know that Visma.net ERP API supports different compression algorithm? We support brotli, gzip and deflate. They can be used by adding Accept-Encoding: <compression type> in your request header. More info and sample code can be found at: Response compression in ASP.NET Core ... View more

Release Notes Documentation Cost price and description of purchase receipts linked to purchase order The fix introduce an issue, we have deployed a rollback to solve this and are working on a new solution.    Due dates for breaking changes Release Notes Documentation Due Breaking change on JournalTransaction endpoint  The POST methods /api/v2/journaltransaction/{journalTransactionNumber}/attachment and /api/v2/journaltransaction/{journalTransactionNumber}/{lineNumber}/attachment are deprecated and will be removed on February 28th 2022. Start using the new methods:  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/attachment  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/{lineNumber}/attachment Feb 28, 2022 ... View more

Release Notes Documentation Creation of new supplier invoices accelerated Earlier, if you had a lot of supplier invoices in your company, the creation of new supplier invoices took a longer and longer time. This has now been fixed. Support for Emailed field in SalesOrder endpoint The Emailed field is now supported in POST, PUT and GET SalesOrder, enabling integrators to update a specific sales order to reflect email communication with the customer regarding this sales order in any external system. "CustomerVATZone" overriden when "soShippingAddress" was included in POST for SalesOrder endpoint Earlier, the "CustomerVATZone" was overridden for the SalesOrder endpoint for versions V1 and V2 when "soShippingAddress" was included in the JSON string for POST. This has now been fixed. Breaking changes on Budget endpoint From January 18th 2022, the following breaking changes will be committed on GET method of the Budget endpoint:  - The Branch and Ledger filters will become mandatory. Now they are specified to be mandatory by documentation, but it is not enforced by implementation.  - The FinancialYear filter will become mandatory  - Now, the branch filter requires being specified either by branch full name (example: BranchID - BranchName), or by branch ID surrounded by quotation marks. It will be simplified to require the branch ID without any other marks. Improved performance on SupplierInvoice endpoint To improve the performance on GET operations, some refactoring has been done in the SupplierInvoice endpoint. Due dates for breaking changes: Release Notes Documentation Due Breaking change on JournalTransaction endpoint  The POST methods /api/v2/journaltransaction/{journalTransactionNumber}/attachment and /api/v2/journaltransaction/{journalTransactionNumber}/{lineNumber}/attachment are deprecated and will be removed on February 28th 2022. Start using the new methods:  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/attachment  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/{lineNumber}/attachment Feb 28, 2022 ... View more

Release notes Description Extended CustomerCreditNote endpoint to support SendToAutoInvoice functionality There is a new endpoint "api/v1/customerCreditNote/{creditNoteNumber}/action/sendToAutoInvoice" to support the created SendToAutoinvoice functionality. Extended Customerinvoice endpoint to support SendToAutoinvoice functionality There is a new endpoint "api/v1/customerinvoice/{customerInvoiceNumbe}/action/sendToAutoInvoice" to support the created SendToAutoinvoice functionality. Extended CustomerDebitNote endpoint to support SendToAutoInvoice functionality There is a new endpoint "api/v1/customerDebitNote/{debitNoteNumber}/action/sendToAutoInvoice" to support the created SendToAutoinvoice functionality. References are not listed  under PurcaseOrder > Purchase Receipts Tab when PurchaseOrders connected to the Purchase Receipts by using the Purchase Receipt Endpoint in API Purchase order link and purchase receipt have been fixed and set behind a feature toggle. (Currently, this is in Beta Testing phase, therefore, not available in every company. Fix will be available for every Financials company in 11.01.2022) Not possible to specify PEPPOL information in Location endpoint in API Earlier, there was no reference to PEPPOL scheme information in the Location endpoint for GET, PUT, POST operations. This has now been fixed. ... View more