August 14, 2026 - August 28, 2026
about 1 hour ago
Container Tracking API
New features
- The Risk Briefs API is now generally available, with public API documentation.
- BoxTrack now displays projected vessel trace points, showing a vessel's expected path ahead of the shipment.
- ZIM booking numbers submitted without the standard prefix are now normalized automatically, improving lookup reliability.
Bugs squashed
- Fixed COSCO shipments where a Last Known Position could stay pinned to a vessel indefinitely after tracking updates stopped, with no discharge signal to clear it.
- Improved OOCL reliability: reference updates no longer fall back to stale or incorrect data when an extraction error occurs, and several additional edge cases are now handled.
- Fixed an OOCL issue where the destination port could be mapped to the origin location and mid-voyage milestones could be dropped when a reference was reprocessed.
- Improved MSC vessel milestone handling.
- Fixed a CMA-CGM issue where the Port of Discharge arrival estimate could be suppressed after terminal activity at the destination, leaving no arrival published.
- Fixed Wan Hai shipments that could show a phantom vessel departure milestone with no vessel, voyage, or facility details.
- Fixed a Maersk issue where origin empty gate-out events were not tagged as empty.
- Restored Hyundai Merchant Marine (HMM) container-only lookups after a regression reduced their success rate.
- Improved handling of barge and other waterway legs for Hapag-Lloyd shipments.
- Fixed duplicate container events being returned in tracking responses.
- Fixed inconsistent type codes on transshipment-stop milestones.
- Added Teamglobal Logistics to the List Carriers endpoint.
- Fixed an issue where a small percentage of organization-level webhook events could be dropped.
- Fixed a Carrier Performance report issue where the same carrier could appear as both the best- and worst-performing.
- Fixed projected vessel trace showing positions for vessels after they had transshipped.