This webhook is activated when an inbound scan has occured. It will show what barcode that has been scanned and what orders and cargo it has been matched with
The request from the webhook will look like this:
{
"webhookId": "699ce35184f53e0b15a6d072",
"name": "inboundScan",
"sent": "2026-02-23T23:31:29.002Z",
"created": "2026-02-23T23:31:29.025Z",
"data": [
{
"orderId": null,
"orderNumber": null,
"requisition": null,
"barcode": "A",
"cargoId": null,
"identifier": "vehicle1",
"locationName": "DB",
"doneAt": "2026-02-23T22:00:00.000Z"
},
{
"orderId": "696a7056e2441e005e35881c",
"orderNumber": "TESTING-CAS-20251211-1",
"requisition": null,
"barcode": "TEST-ME-20260209",
"cargoId": "696a7056e2441e005e35881e",
"identifier": "vehicle1",
"locationName": "DB",
"doneAt": "2026-02-23T22:00:00.000Z"
}
]
}| Key | Description |
|---|---|
| orderId | The order id that has been matched with the scanned barcode. This value can be null if no orders was matched |
| orderNumber | The order number that has been matched with the scanned barcode. This value can be null if no orders was matched |
| requisition | The order requisition that has been matched with the scanned barcode. This value can be null if no orders was matched |
| barcode | The value of the barcode that got scanned |
| cargoId | The id of the cargo that matched with the scanned barcode. This value can be null if no cargo was matched |
| identifier | A value the user who does scanned can set so it's possible to identify a group of scans |
| locationName | The name of the location that the user has scanned the barcode at |
| doneAt | The time when the scanned was registered |