We’ve implemented a new feature that API Endpoints available at Visma.net ERP API Documentation, can be invoked in an asynchronous mode by using the new “Background API” functionality. (Version: 8.88.0)  This can be achieved by adding an extra request header “erp-api-background: “WebhookURL”  to your request.   If this additional “request header” is provided in your request, our servers  will "intercept" the API request before it reaches the Endpoint. The request will be persisted in our backend. All our application web servers will regularly pull queued requests and process them in the background. This processing is not taking place in a web context, and therefore it is not prone to web exceptions like timeouts etc.    In this way, with this new feature, potentially long-running operations can be performed more effectively.    Once the request has been processed, the API Client will be notified with the webhook notification if “erp-api-background” request header had been provided with “webhookURL” value in your request.   This webhook notification will contain information about, “stateLocation” of the operation(status of the background operation) and “ContentLocation”  that where the response can be picked up, in other word, where the API Client can GET the result of the request that has recently been made.(if it has any content aka ResponseBody)   If the “erp-api-background” request header value set as “none” Webhook notification will not be invoked.  In any case, every queued API request will be assigned an ID that will be present in the immediate “202-Accepted” response to the client.  This response also contains a "stateLocation" address that the client can call at any time to check what is the status of the background operation.  "contentLocation" address that points to the readily formatted and stored response body of the operation if it has any content to be returned.   If the endpoint today is asynchronous,  meaning that if it is immediately returning a “202-Accepted” HTTP response and starts the actual job in the background, such as “Action” based operations. (Endpoint URL: …/action/…),     Currently,  the new "Background API" system is also unable to receive the state of the document when the action based request invoked. Therefore, we’re unable to determine whether the “action” based process succeeded or the state of the document changed without making an additional GET request to see the actual status of the document. However, this topic is already in our development plan. (Endpoint logic should be "synchronous" so that, waiting for the actual job to be done, to inform the client accordingly.)   Example request: "Request Headers erp-api-background : yourWebhookURL" Key  Value ipp-application-type Visma.net Financials ipp-company-id "ERP CompanyID" Content-Type application/json Authorization "yourToken" erp-api-background "yourWebhookURL"   GET: "Customer  Invoice" Request URL: /api/v1/customerinvoice?pageNumber=1&pageSize=100 HTTP Response: “202-Accepted” Response Body: Received Webhook Notification: GET: "stateLocation" Request URL: /api/v1/background/{id} HTTP Response: ”200-OK” Response Body: GET: "contentLocation" Request URL: api/v1/background/{id}/content HTTP Response: ” 200-OK” Response Body: Contains the “GET - CustomerInvoice” data. --------------------------------------------------------------------------------------------------------------------------------------- POST: “Customer Invoice” Request URL: “/api/v2/customerinvoice” HTTP Response: “202-Accepted” Response Body: Contains request “ID” and “stateLocation” Received Webhook Notification: GET: "stateLocation" Request URL: /api/v1/background/{id} HTTP Response: ”200-OK” Response Body:  --------------------------------------------------------------------------------------------------------------------------------------- PUT: "Customer Invoice" Request URL: /api/v1/customerinvoice/{invoiceNumber} HTTP Response: “202-Accepted” Response Body: Contains request “ID” and “stateLocation” Received Webhook Notification: GET: “stateLocation” Request URL: /api/v1/background/{id} HTTP Response: ”200-OK” Response Body: --------------------------------------------------------------------------------------------------------------------------------------- "Request Headers erp-api-background : None" Key Value ipp-application-type Visma.net Financials ipp-company-id "ERP CompanyID" Content-Type application/json Authorization "yourToken" erp-api-background "None"     ℹ️ Webhook notification will not be invoked, State & Content Location logic will be the same as request examples shared above.  ---------------------------------------------------------------------------------------------------------------------------------------   Please feel free to contact us (Financials ERP API Support) if you need any further information. ... View more

Release date for 8.88.0 version has been planned as 15/03/2022. Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release.   Release Notes Documentation New “Background API” functionality Now all API endpoints available at Visma.net ERP API documentation can be invoked in asynchronous mode by using the new “Background API” functionality. Documentation can be found here. Improved performance on GET ALL CustomerPayment endpoint The performance of the CustomerPayment endpoint has been improved.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Location endpoint for PUT operation PUT Location endpoint will from version 8.91.0 return "404-Not found" instead of "400-Bad request" when the asset is not found. Apr 05, 2022 Breaking change on Inventory endpoint for GET operation Paging will be enforced on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 5000. If you do not specify a page size, you will get 5000 records, and if you try to specify a higher number, you will only get 5000 records. Example: If you do a GET ALL on Inventory, without specifying any paging, you will get the first 5000 records only. Apr 01, 2022 Breaking change on Project endpoint for GET operation Paging will be enforced on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 ... View more

Release Notes Documentation Improved performance on GET ALL Supplier endpoint The performance of the GET ALL Supplier endpoint has been improved, and it is currently in pilot testing. This will be tested by some clients in the beginning. Once the pilot testing phase is completed, the improvement will be enabled for everyone. Line note removed from purchase orders when purchase orders updated via API (PUT) Earlier, when updating purchase orders via API, using PUT method and PurchaseOrder endpoint, the notes were automatically removed. This has now been fixed. PUT inventory endpoint does not update item values for items of type 'SubAssembly' or 'Component Part' Earlier, the PUT inventory endpoint did not update item values for items of type 'SubAssembly' or 'Component Part'. This has now been fixed. Unable to GET "Note" fields via GET Purchase Order Endpoint  Earlier, in some circumstances, the GET Purchase Order endpoint did not return the "Note" fields. This has now been fixed.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Inventory endpoint for GET operation Paging will be enforced on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Inventory, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 Breaking change on Project endpoint for GET operation Paging will be enforced on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 ... View more

Release date for 8.87.0 version has been planned as 08/03/2022. Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release. Release Notes Documentation Improved performance on GET ALL Supplier endpoint The performance of the GET ALL Supplier endpoint has been improved, and it is currently in pilot testing. This 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. Line note removed from purchase orders when purchase orders updated via API (PUT) Earlier, when updating purchase orders via API, using PUT method and PurchaseOrder endpoint, the notes were automatically removed. This has now been fixed. PUT inventory endpoint does not update item values for items of type 'SubAssembly' or 'Component Part' Earlier, the PUT inventory endpoint did not update item values for items of type 'SubAssembly' or 'Component Part'. This has now been fixed. Unable to GET "Note" fields via GET Purchase Order Endpoint  Earlier, in some circumstances, the GET Purchase Order endpoint did not return the "Note" fields. This has now been fixed.     Due dates for breaking changes Release Notes Documentation Due Breaking change on Inventory endpoint for GET operation Paging will be enforced on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Inventory, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 Breaking change on Project endpoint for GET operation Paging will be enforced on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 ... View more

Release Notes Documentation Improved performance on GET Inventory endpoint [Pilot Testing] The performance of the GET Inventory endpoint has been improved, and it is currently in Pilot Testing. This will be tested by the volunteered clients. Please contact the Partner Service from your country if you would like to volunteer. Once the pilot testing phase is completed, the improvement will be enabled for everyone. (Will be announced) Performance improvements on Dimension endpoints The performance on the following Dimension endpoints has now been improved: GET/controller/api/v1/dimension/{dimensionId} GET/controller/api/v1/dimension/{dimensionId}/{segmentId} GET/controller/api/v1/dimension/{dimensionId}/{segmentId}/{valueId} GET/controller/api/v1/dimension/{dimensionId}/{segmentId}/publicid/{publicId} Wrong "Location" URL returned after successful POST CustomerInvoice V2 request Earlier, the wrong "Location" URL was returned after a successful POST CustomerInvoice V2 request. This has now been fixed. "GreaterThanValue" query parameter not working with GET Shipment endpoint Earlier, the "GreaterThanValue" query parameter was not documented as being deprecated for the GET Shipment endpoint. This has now been fixed. Unable to update a customer's "Invoice Address" fields via PUT Customer endpoint Earlier, in some circumstances, the PUT Customer endpoint did not update the customer's "Invoice Address" fields. This has now been fixed. The "Packages" field exposed via ShipmentDTO (GET Shipment) is not populated Earlier, the GET Shipment endpoint did not populate the "Packages" field. This has now been fixed. Activate feature "Transfer Order" to the "Transfer Receipt" via Purchase Receipt endpoint Earlier, adding "Transfer Order" to the "Transfer Receipt" via the Purchase Receipt endpoint was not possible. Now, you are able to use POST operation via PurchaseReceipt endpoint to create transfer receipts via API. Update notes via API (PUT) on SupplierInvoice when status is "Open" Earlier, updating notes via API (PUT) on SupplierInvoice endpoint, when the status of the document was "Open", was not possible. This has now been fixed. Cost price and description of purchase receipts linked to purchase order Earlier, when you created a purchase receipt and linked it to a purchase order with API, the cost price and description were retrieved from the item and not from the purchase order rows as they should. This has now been fixed, and the cost price and description are retrieved from the purchase order rows for each item. Breaking change on JournalTransaction endpoint   The POST methods /api/v2/journaltransaction/{journalTransactionNumber}/attachment and /api/v2/journaltransaction/{journalTransactionNumber}/{lineNumber}/attachment are deprecated and has been removed. Start using the new methods:  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/attachment  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/{lineNumber}/attachment     Due dates for breaking changes Release Notes Documentation Due Breaking change on Inventory endpoint for GET operation Paging will be enforced on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Inventory, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 Breaking change on Project endpoint for GET operation Paging will be enforced on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 ... View more

Release date for 8.86.0 version has been planned as 01/03/2022. Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release.   Release Notes Documentation Improved performance on GET Inventory endpoint [Pilot Testing] The performance of the GET Inventory endpoint has been improved, and it is currently in Pilot Testing. This will be tested by the volunteered clients. Please contact the Partner Service from your country if you would like to volunteer. Once the pilot testing phase is completed, the improvement will be enabled for everyone. (Will be announced) Performance improvements on Dimension endpoints The performance on the following Dimension endpoints has now been improved: GET/controller/api/v1/dimension/{dimensionId} GET/controller/api/v1/dimension/{dimensionId}/{segmentId} GET/controller/api/v1/dimension/{dimensionId}/{segmentId}/{valueId} GET/controller/api/v1/dimension/{dimensionId}/{segmentId}/publicid/{publicId} Wrong "Location" URL returned after successful POST CustomerInvoice V2 request Earlier, the wrong "Location" URL was returned after a successful POST CustomerInvoice V2 request. This has now been fixed. "GreaterThanValue" query parameter not working with GET Shipment endpoint Earlier, the "GreaterThanValue" query parameter was not documented as being deprecated for the GET Shipment endpoint. This has now been fixed. Unable to update a customer's "Invoice Address" fields via PUT Customer endpoint Earlier, in some circumstances, the PUT Customer endpoint did not update the customer's "Invoice Address" fields. This has now been fixed. The "Packages" field exposed via ShipmentDTO (GET Shipment) is not populated Earlier, the GET Shipment endpoint did not populate the "Packages" field. This has now been fixed. Cost price and description of purchase receipts linked to purchase order Earlier, when you created a purchase receipt and linked it to a purchase order with API, the cost price and description were retrieved from the item and not from the purchase order rows as they should. This has now been fixed and the cost price and description are retrieved from the purchase order rows for each item. Activate feature "Transfer Order" to the "Transfer Receipt" via Purchase Receipt endpoint Earlier, adding "Transfer Order" to the "Transfer Receipt" via the Purchase Receipt endpoint was not possible. Now you are able to use POST operation via PurchaseReceipt endpoint to create transfer receipts via API. Update notes via API (PUT) on SupplierInvoice when status is "Open" Earlier, updating notes via API (PUT) on SupplierInvoice endpoint, when the status of the document was "Open", was not possible. This has now been fixed.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Inventory endpoint for GET operation We will enforce paging on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Inventory, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 Breaking change on Project endpoint for GET operation We will enforce paging on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 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 March 1st 2022. Start using the new methods:  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/attachment  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/{lineNumber}/attachment Mar 1, 2022 ... View more

Release Notes Documentation Improved error response for the PUT stocktakeV2 endpoint PUT stocktakeV2 now has an improved error response, which will help integrators solve invalid entries. The Swagger documentation for this endpoint is updated with these improvements. New parameter for filtering and sorting of documents via SupplierInvoice endpoint Document "Status" has been added as a filtering parameter via the SupplierInvoice endpoint to improve filtering and sorting of documents in Visma.net ERP. 401 Unauthorized error message on $Batch endpoint For a while, batch http requests to api/v1/$batch have failed with 401-Unauthorized. The workaround has been to set authentication and authorization headers on every sub request. This has now been fixed so that all headers from the main request will be copied to every sub request if they are not already present.     Due dates for breaking changes Release Notes Documentation Due Breaking change on Inventory endpoint for GET operation We will enforce paging on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Inventory, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 Breaking change on Project endpoint for GET operation We will enforce paging on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 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

We're currently planning to roll out an improvement that we gained performance on the GET Inventory Endpoint. This is part of our ongoing effort to improve our code base and promote quick and robust API transactions. Release information in detail regarding when the performance improvement on the GET Inventory Endpoint is available will be announced soon.   What is changing and how it will benefit your Inventory Endpoint usage ? Pagination will be enforced on the GET Inventory Endpoint on "01.04.2022"  ℹ️ (Update: The default page size has been adjusted to 5000.) Back then, the metadata "TotalCount" value returned was wrong when the "Attributes" filtering used together with the Pagination, therefore we had to suspend the pagination enforcement on the GET Inventory Endpoint. With the new implementation, Query filtering with "Attributes" will be working as expected when Pagination is used. Improved performance on GET Inventory Endpoint ... View more

Release date for 8.85.0 version has been planned as 22/02/2022. Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release. Release Notes Documentation New parameter for filtering and sorting of documents via SupplierInvoice endpoint Document "Status" has been added as a filtering parameter via the SupplierInvoice endpoint to improve filtering and sorting of documents in Visma.net ERP. Improved error response for the PUT stocktakeV2 endpoint PUT stocktakeV2 now has an improved error response, which will help integrators solve invalid entries. The Swagger documentation for this endpoint is updated with these improvements. 401 Unauthorized error message on $Batch endpoint For a while, batch http requests to api/v1/$batch have failed with 401-Unauthorized. The workaround has been to set authentication and authorization headers on every sub request. This has now been fixed so that all headers from the main request will be copied to every sub request if they are not already present.     Due dates for breaking changes Release Notes. Documentation Due Breaking change on Inventory endpoint for GET operation We will enforce paging on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Inventory, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 Breaking change on Project endpoint for GET operation We will enforce paging on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 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 The performance of the GET Supplier Invoice endpoint has been improved The performance of the GET Supplier Invoice endpoint has been improved, leading to quicker response time. This has been in pilot testing for 2 weeks now and will be enabled for all customers with version 8.84.0 of Visma.net ERP. GET CustomerInvoice endpoint returns the same value for fields 'originatorDocRef' and 'contractorDocRef'.   Earlier, when using the GET customerinvoice endpoint, the fields originatorDocRef and contractorDocRef got the same value. This has now been fixed. ... View more

Release date for 8.84.0 version has been planned as 15/02/2022. Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release.   Release Notes Documentation The performance of the GET Supplier Invoice endpoint has been improved The performance of the GET Supplier Invoice endpoint has been improved, leading to quicker response time. This has been in pilot testing for 2 weeks now and will be enabled for all customers with version 8.84.0 of Visma.net ERP. GET CustomerInvoice endpoint returns the same value for fields 'originatorDocRef' and 'contractorDocRef'.   Earlier, when using the GET customerinvoice endpoint, the fields originatorDocRef and contractorDocRef got the same value. This has now been fixed.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Project endpoint for GET operation We will enforce paging on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 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 Improved performance for GET inventory (Rolled Back due to inconsistencies caused) The performance of the GET inventory endpoint has been improved, leading to quicker response time. New compression option for the API Earlier, only deflate and gzip compression was supported when fetching data from the API. Now Brotli compression has also been added. It can be used by adding the following Request Header: Accept-Encoding: br Brotli algorithm is better than gzip and deflate and will improve API performance when used. Performance improvements on GET Project endpoint The performance on the GET Project endpoint has now been improved.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Project endpoint for GET operation We will enforce paging on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only. Apr 01, 2022 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