to get a personalized navigation.
to get a personalized navigation.
Suddenly the webhook returns resourceURI without the SalesorderType. In this case the salesorder is not SO , but WE, therefore it cant find the salesorder.
Any changes made since 28.01.2023?
Webhook 30.01.2023 - cant find salesorder
[ { "notificationId": "85a0d503-bb84-4844-af6a-0c40d87b184e", "contexId": "1089046", "event": "salesorder_changed", "relativeResourceUri": "api/v1/salesorder/36578", "resourceUri": "https://integration.visma.net/API/controller/api/v1/salesorder/36578", "timeStamp": "638106744407030000", "action": "monday" } ]
Webhook ok 28.01.2023 - can find salesorder
[ { "notificationId": "c1d5e5e3-4a41-44fc-a9b5-9501bf64cf53", "contexId": "1089046", "event": "salesorder_changed", "relativeResourceUri": "api/v1/salesorder/SO/011730", "resourceUri": "https://integration.visma.net/API/controller/api/v1/salesorder/SO/011730", "status": "Open", "timeStamp": "638105075463130000" } ]
Hi,
The latest change to the webhooks was released the 17th Jan: [Release Notes] - Visma.Net API 9.30.0 - 17.01.2023
Are you only seeing this issue on one company?
We'll have a look at it and inform the development team.
That is not true. Last week the (swagger) version was 9.30.00.1004 now it is 9.30.00.1005.
Also the webhook changes introduced the 17:th (tenantid etc) are no longer included in the webhook.
(and my azure webhook receiver suddenly started working on friday without changes on my side)
Copyright © 2022 Visma.com. All rights reserved.