Unclear Status Codes in Webhook Notifications

[Leo Hämäläinen]

We have encountered an issue with webhook notifications from Visma.net related to shipments. Normally, the status field in the notifications contains clear values such as:

• Open 

• Hold

• etc.

Recently, however, we have started receiving unfamiliar status values such as:

• "N"

• "F"

• "H"

These are not known to us and do not match the previously seen status values.

Below is an example of a webhook notification for shipment 071024, where the status is "N":

[
  {
    "notificationId": "92b718f7-1aa2-4e98-b6d1-f4f63a741351",
    "contextId": "***",
    "event": "shipment_changed",
    "action": null,
    "status": "N",
    "resourceId": "071024",
    "resourceUri": "https://finance.visma.net/1048001005/api/v1/shipment/071024",
    "relativeResourceUri": "/api/v1/shipment/071024",
    "timeStamp": "638833316812300000",
    "ApiClientId": null,
    "TenantId": "***",
    "IsScheduler": false,
    "ConnectId": "72d0c556-e68e-4c6f-a64d-c9fdee3be02d"
  }
]

Could you please confirm what these statuses ("N", "F", "H") represent, and whether they are newly introduced values?
If this is due to a change in the integration behavior, we would appreciate any additional information or documentation you can provide.

[Suzdar Ibrahim]

Hi, @adrianm @Leo Hämäläinen 

Hi,

Issue should be resolved now 🙂

1. Timestamps are corrected from String to Numeric

2. Status in payload are corrected from one letter to the correct word. 

3. State location in payload in background Api are corrected. 

---

After the switch and reading logs we have found two other issues. We will solve these also, and aim to release it in the next version next week.

1. Action properties are empty for some events

2. Background API response header location has the wrong ID. 

BR,

Suzdar

[Suzdar Ibrahim]

Hi @adrianm  & @Leo Hämäläinen ,

We are planning on releasing a hotfix for this during the work hours tomorrow and let me know if the issue is still there by end of tomorrow.

Thanks!

BR,

Suzdar

[Suzdar Ibrahim]

Hi,

We are investigating this and will update this thread when we have news regarding this.

[adrianm]

That is not the only change:

1. timestamp is now a string, not a number

2. resourceUri can no longer be used to fetch the resource

(visma migrated webhooks to a new platform this morning. The migration was announced a long time ago but the actual date has not been published. It was supposed to be transparent except IP-adresses)