A new endpoint `post_pre_alert` has been added to upload the airwaybill PDF together with key metadata (estimatedTimeOfArrival, airWaybillNumber and grossWeight). On success the pre-alert is stored, the manifest is locked and parcel aggregates are returned. See the updated Postman collection and API documentation for the full request and response format.
For all airwaybills manifested from 01-01-2026 onwards a successful `post_pre_alert` call is mandatory before submission. Manifests for airwaybills without a pre-alert will no longer be able to be uploaded to the correct customs instance. Please update your integration before this date.
To remove duplicated data the action 101 response will change from 01-01-2026. Label details such as `shipmentID`, `barcode`, `labeltype`, `encodeType`, `content`, `carrierId` and `carrierOptionId` will only be returned inside the `labels` array and will be removed from the top level of the response object.
The new `post_pre_alert` endpoint and the updated 101 response format are available ahead of time so you can migrate safely. From 2026 onward only the new behaviour will be supported.
The parameter `waybill` has been renamed to `transportNumber`. For backwards compatibility, `waybill` will still work until 28-11-2025. After this date, only `transportNumber` will be supported.
A new parameter `transportType` has been introduced to define the transport mode. Supported values are: **CMR** (road transport), **AWB** (air transport), and **B/L** (bill of lading).
Parameter requirements now vary depending on the selected `transportType`. Refer to the updated API documentation for detailed requirements per transport type.
The `B/L` (bill of lading) option is not yet implemented but will be added in a future update.
Waybill tracking and parcel tracking have been separated. To enable waybill tracking, a new parameter has been introduced: flight_tracking_setting – accepts values: only, include, or exclude. By default, this setting is exclude.
The result structure has been cleaned up. The following fields have been deprecated: Statussen, statussen, errors, LastStatus, CarrierInformation, carrierInformation, Items -> label. Refer to the updated result format in the API documentation.
Language selection has been added. Supported languages are: NL (Dutch) and EN (English). Usage example: ?lang=en
Bulk tracking by barcode is now supported, with a limit of 1000 barcodes per request. Example format: ["Barcode1", "Barcode2"]
When a barcode does not exist, it will be listed under the new notFound array: "notFound": ["NonExistentBarcode"]. In bulk requests, all invalid barcodes will appear here, and valid ones will return as usual.
The items array has been reordered so that the newest status appears first. A new field, itemNumber, has been added to allow easy reversal if needed.
The response header is now set to: Content-Type: application/json; charset=utf-8
Tracking can now be done by: waybill (only one allowed per request), box (up to 10 allowed per request), barcode (default if no type is specified, up to 1000 allowed per request). Note: This applies only if customs data has been uploaded. Use the parameter ?type=waybill, box, or barcode.
A new parameter tracking_details has been added. It allows control over the level of returned data: minimal, lastStatus, full.