Hi @adrianm, “What return code for timeout will be?”  504 Gateway Timeout. “If the timeout happens on PUT/POST, will the operation also be cancelled?” This depends on the business logic behind the endpoint. If there is no actual checking there - within the transaction or process - that the client still is connected, then the transaction should go through, even though the client got a timeout response. “OpenApi and versions” "v1" as version has been the same always and will probably still be for a while. It can be looked upon as the version of the ERP API, not to be confused with the v1 or v2 in the url, which points to a particular endpoint version, or the OpenAPI specification version which is the version of the (swagger) specification format.   Please let us know if you have any further questions.   Hi @thingsio ,  “I assume this will not change the token request URL too?” You are correct, the URL for the request token will stay the same.(https://connect.visma.com/connect/token)   Hi @jacob, “https://salesorder.visma.net/api/v3/ Wil this also move to https://finance.visma.net/ ?” The URL for Visma Net SalesOrder API will remain the same.(https://salesorder.visma.net/api/v3/) ... View more

We have this issue too. We do the following:   create an empty purchase receipt: {  "receiptType": {  "value": "PoReceipt"  },  "supplierId": {  "value": "C00059"  },  "date": {  "value": "2025-01-31"  } } After doing this we get a purchasereceipt number which is not visible in the Visma UI. Correct?   create a purchase orderline by using linenumber from purchaseorder {     "purchaseOrderLines": [         {             "orderNbr": "PO11250001",             "lines": [                 {                     "lineNbr": "1"                 }             ]         }     ] }   Linenumber 1 in the purchaseorder exists but we are getting error: {     "message": "Error adding purchase orders to receipt: Purchase order line 1 could not be found for order number PO11250001 " } ... View more

Line numbers are needed to keep an unique identifier for a line. InventoryId does not work as a unique identifier. In some shipments it will be the same InventoryId for several lines. A get-request to catch the lineNumber before the put-request is then what you can do.    If you think lineNumbers is not effective for you and think inventoryId can be useful, you can make a post under the Ideas section of this forum. ... View more

Hi, we also have a need to link directly to for example: purchase receipt orders, inventory adjustments etc. Because we pull information from Visma API's in other apps. we also want to link directly from other apps. to make it more convenient for users. For me the second part of the URL is pretty unclear:   https://finance.visma.net/1011011001   This number changes once and a while and I don't think it's a version number which can be found in the Swagger documentation.   If it can be found in the swagger, to what exactly are you referring in that documentation? A method or something else? ... View more

For suggestions for improvement, we recommend that you create a post in the Ideas section of the forum. This allows other users to vote for your issue, which raises the urgency the development team will have when evaluating your suggestion.   ... View more

Hi, yes that is the correct URL, thanks for the update! ... View more

Hi! To do multiple adjustments you add as many of the "issueLines"-objects as you wish in the array of the issueLines. {     "issueLines": [         {             "operation": "Insert",             "tranType": {                 "value": "Issue"             },             "branchNumber": {                 "value": "11"             },             "warehouseId": {                 "value": "gro"             },             "lineNumber": {                 "value": 1             },             "inventoryNumber": {                 "value": "10001"             },             "quantity": {                 "value": 5             },             "reasonCode": {                 "value": "2"             }         },         {             "operation": "Insert",             "tranType": {                 "value": "Issue"             },             "branchNumber": {                 "value": "11"             },             "warehouseId": {                 "value": "gro"             },             "lineNumber": {                 "value": 2             },             "inventoryNumber": {                 "value": "10001"             },             "quantity": {                 "value": 5             },             "reasonCode": {                 "value": "2"             }         }     ] }   Hope this answered your question. Kind regards Sandra Anté ... View more

Hi,   We use https://integration.visma.net/API/controller/api/v1/inventoryissue and the following data according to the documentation:   {     "issueLines": [{         "operation": "Insert",         "tranType": {             "value": "Issue"         },         "warehouseId": {             "value": "gro"         },         "lineNumber": {             "value": 0         },         "inventoryNumber": {             "value": "13003"         },         "quantity": {             "value": 7         },         "uom": {             "value": "STUK"         },         "reasonCode": {             "value": "2"         }     }],         "date": {         "value": "2023-05-03T10:07:16.563"     }      }   For any logistics company it is really important to be able to see a date when an Inventory issue is changed.   Can we get back to the original problem? How can we change the inventory by using the API and also show a date when that is done?   Cheers and thanks! ... View more