Hello Jyrki,    Visma.net ERP API uses OAuth 2.0 bearer tokens (OAuth 2.0 Authorization Code Grant) to authenticate API calls.  This flow generate a token on behalf of the Visma.Net Financials user. The authenticated user's access rights(Financials Administrator-Financials User) in Visma.net determine that the generated token can be used on which company. (The user to whom the token belongs needs to have the aforementioned roles in that company in order to access via the API.) Supposing that there is X ISV has 2 customers and integration running like 1st Customer: a-b-c companies 2nd customer: d-e-f companies -When token request made from the same API CLIENT ID: Each company should have its own Visma.Net user to generate a token and this token will work as covering the companies based on the authenticated users granted roles on the Visma.Net Financials. The token belongs to visma.net USER and can be used on any company where the user has "Financials User"-"Financials Administrator" role granted. The API integrator should provide the interface for the client/user to interact with the web browser, and each user should be authorized to generate a token by their own credentials. If there are multiple companies, you should ask the user to select/specify which company is the integration made for. This can be a one-time set-up at the beginning, then once you generate the token you can store it for that user and can be used on the companies which one the user has access to. You can Get the companies available for the used token/Integration user via Context endpoint for mapping, user/token = Financials Company https://integration.visma.net/API/ resources/v1/context Currently, Token Life Cycle does not have any specific interval, it's planned to facilitate as never expires. Each consecutively generated token automatically invalidates the recently created one. (Request made from the Same CLIENT ID & the Same Visma.Net Financials user for all integrations/company) ❌ ISV / Integrator should ask their ERP Customer to have a different user for each integration/company. In this way, the integrator will use the same "client_Id" for all the integrations, but the ERP Customer will be using a different user for each company during the authorization. This is the recommended setup for our ISVs for obtaining a token while using the same ClientID for all the integrations.✔️  In this way, If something goes wrong with one of the integrations (e.g. token gets invalidated), ISV generates a new token, then the other integrations will not be affected thus ISV can continue to use their existing token/s.   Please let us know if you need any further clarification. ... View more

Hello Marius,  currently, the "Cash Return" is not exposed via the API, therefore we're unable to realize this operation in the API. However, this request is in the backlog and there is no development information has been emerged yet. ... View more

Hello Roland,  thank you for the information you've provided. We're able to reproduce the issue, we've informed the relevant team for the investigation.    Steps to reproduce: 1) Create "TR" Type Sales Order in the Financials ERP (ScreenId=SO301000) 1.1) Create Shipment via Actions > Create Shipment in the SalesOrder screen. 2) Confirm shipment via Actions > Confirm Shipment in the Shipment screen.(ScreenId=SO302000) 2.1) Update Inventory via Actions > Update Inventory in the Shipment (ScreenId=SO302000) 3) Create "Transfer Receipt" type Purchase Receipt (ScreenId=PO302000) 3.1) Add TR type SalesOrder to the "Transfer Receipt" via "Add Order" button in the Purchase Receipt ✔️   4) Add TR type SalesOrder to the "Transfer Receipt" via POST Purchase Receipt API ❌ POST > https://integration.visma.net/API/controller/api/v1/PurchaseReceipt Returns: "Error creating purchase receipt. Error: 'ShipAddressID' cannot be empty."   { "lines": [ { "operation": "Insert", "transferOrderType": { "value": "TransferOrder" }, "transferOrderNbr": { "value": "000519" }, "transferOrderLineNbr": { "value": 1 } } ], "receiptType": { "value": "TransferReceipt" }, "warehouseId": { "value": "2" } }     ... View more

Hello,  we confirm that the "Body" field represented in the "InventoryDto" for GET All & Specific Inventory Endpoints is not returned to the GET response.  This has been reported to the development team and currently being investigated.  ... View more

Hello,  @Roland van Belle - Consolit wrote: 1. The user makes a salesorder of type TR by hand in the system.  -If TransferOrder has been created in the UI please send us a print screens of the "Transfer Order" where we can see the document header - lines,  "Delivery Settings" and  "Shipments" tab.   Is this error only occurring with that specific "TransferOrder" ? Have you tried creating a new one by following the same steps ? ... View more

Hello,  are you referring to the request's > Response Body or to a specific field ?    Please send us your API transaction details. API Client ID Financials ERP Company ID Used API Endpoint URL Returned Http Status Code A Print screen highlighting the area  / what part is missing / supposed to be returned in your request.  Thanks. ... View more

Thanks. Could you also describe the followed workflow for each step in detail ?  1) How "Transfer Order's been created via API or Financials ERP UI ?     -If via API: Send us the used POST JSON   -If in the UI: Send us a print screens of the "Transfer Order" where we can see the document header - lines,  Delivery Settings and  Shipments tab. 2) How "Shipment" is processed ?  3) Have you tried adding the "Transfer Order" to the "Transfer Purchase Receipt" by using "Add  Transfer" option in the Purchase Receipt, Financials ERP UI ?     ... View more

Hello,    Visma.net ERP API tokens Token Life Cycle does not have any specific interval, it's planned to facilitate as never expires. Each consecutively generated token automatically invalidates the recently created one. If the request made from the Same CLIENT ID & the same Visma.Net Financials user for all integrations/company.    Do you know what is your "API Client_ID" that the token generated and used in event subscription ? Also, do you recall what email address registered with that API Client ? Or, Financials ERP Company ID, used subscription & event and hookUri ? If you could provide us information about them, we can try to remove the subscription or alternatively reset the API Client so that you can generate a new token.  ... View more

Hello,    have you saved the Order after entering the data in the UI ? Also, it seems all the lines set "0" quantity and without unitPrice / cost, could you adjust that according to what is sent in the JSON and retry ? ... View more

Hello, please share the details of your API Transaction/s. Used API Endpoint URL / Method Returned Http Status Code Returned Response Body (Error Message) If this is a POST/PUT request, then Used RAW JSON script has to be attached Thanks. ... View more

Please try creating the sales order in the Financials ERP UI with the same values / inventory in the lines sent via the API to see if the system highlights any error that can help to find out the issue.  Please also inform us about the details of your custom order type (EB) by sending print screens from Order Types panel (ScreenId=SO201000) in the Financials ERP UI Example: Including, General Information & Template settings tab for "EB"    Thanks. ... View more

Hello Arne,    in the first place, the syntax of the JSON you've shared is incorrect. Data should be passed with key & value pairs. Please see the swagger documentation (POST /controller/api/v2/salesorder - Example Value ) and the example JSON below.    { "orderType": { "value": "SO" }, "hold": { "value": true }, "date": { "value": "2021-08-01T00:00:00" }, "requestOn": { "value": "2021-08-31T00:00:00" }, "customer": { "value": "10034" }, "description": { "value": "Inngående ordre fra eBoks" }, "soBillingAddress": { "value": { "overrideAddress": { "value": true }, "addressLine3": { "value": "0" } } }, "lines": [ { "operation": "Insert", "alternateID": { "value": "6796" }, "subaccount": [], "externalLink": " ", "inventoryNumber": { "value": "1" }, "uom": { "value": "STK" }, "quantity": { "value": 1.0 }, "note": { "value": "6796 | | 5798002040708 | Plads betales for: 000 MB | Plads total: 000 MB" } }, { "operation": "Insert", "alternateID": { "value": "11252" }, "subaccount": [], "externalLink": " ", "inventoryNumber": { "value": "122" }, "uom": { "value": "STK" }, "quantity": { "value": 2.44 }, "note": { "value": "11251 | | 5798002040708 | Plads betales for: 000 MB | Plads total: 000 MB" } } ] }   It appears that the error might be related to one of the inventories ("inventoryNumber")  used in the JSON. Please make sure none of them have a status other than "Active" in the Financials ERP UI. (Stock Items:ScreenId=IN202500) & (Non-stock Items:ScreenId=IN202000)             ... View more

Hello,    please send us a print screen which is showing the current values of the document/fields that you're trying to update via the API.  (Document header, ComponentLines, Allocations) ... View more

Hello, when you're posting an API issue on the community, please share clarified information which belongs to your API Transaction/s. Used API Endpoint URL / Method Returned Http Status Code Returned Response Body (Error Message) If this is a POST/PUT request, then Used RAW JSON script has to be attached These pieces of information are crucial for us to be able to help you, diagnose the case.    We also recommend reviewing the following article: API incidents - Troubleshooting and reporting Thanks. ... View more

Hello, the issue experienced was related to the https://status.visma.com/incidents/xszmqh2wwbw6 which has been resolved in  09:59  CET 24.01.2022. If you encounter any problem concerning the same case, please contact us.  Thanks.    ... View more

Hello,    we confirm the issue that Response Headers {Location}  indicates the URL of the newly created resource with v2, although GET Customer Invoice Endpoint is currently available in v1. This has been passed on to the responsible development team to be analysed. Information on when this can be fixed, will be shared in the "News" - Related version's Release Note once the fix details are emerged. ... View more

Hello,   the following endpoint can be used for (POST) operation. It is corresponding with "ScreenID:AR301000" - Customer Invoice > Credit Note Type in the Financials ERP UI.  Endpoint documentation can be found at https://integration.visma.net/API-index/   ... View more

Hello, this has been planned to be fixed in Visma.net Financials API updates for version 8.81.0 Please follow the "News" section of the community for the final release-notes. ... View more

While this is being investigated,  https://integration.visma.net/API/controller/api/v1/purchaseorderbasic  can be used as a workaround, since GET All -  purchaseorderbasic Endpoint returns both Header & Line level note fields.  ... View more

Hello Teemu,    could you please also specify the operation (GET-PUT-POST) that you'd like to get "Replenishment class" field exposed via the Inventory Endpoint ?  ... View more