September 25, 2026 - October 9, 2026
about 1 hour ago
Container Tracking API
New features
- SITC bills of lading submitted with a non-carrier prefix are now recognized and normalized automatically, improving lookup reliability.
- Milestones at the same location are now returned in physical journey order (for example, vessel arrival before gate out) when two events share the same timestamp, or when Hapag-Lloyd reports an event with a date but no time.
Bugs squashed
- Resolved intermittent update failures for Hapag-Lloyd references and improved reliability for parent references.
- Fixed an OOCL regression where the destination port could resolve past the Port of Discharge to the place of delivery, dropping the Port of Discharge name and arrival estimate.
- Fixed OOCL Port of Discharge arrivals being labeled as transshipments, and a missing container location on "available for pickup" milestones.
- Fixed a Yang Ming issue where laden gate-out events were always labeled "Gate out from destination port," which could show the origin as the destination port.
- Auto-unsubscribe no longer triggers early on new container journeys because of the shipment's own first milestone.
- Terminal and rail events are now scoped to the reference's own journey, so they no longer attach to unrelated shipments.
- Fixed terminal events from Montreal Gateway and GCT terminals being attributed to the wrong containers when a container number was missing or partial.
- Fixed Last Known Position lagging behind the latest vessel trace for vessels in open ocean; it now uses the newest available position, including satellite position reports.
- Fixed incorrect
item_countandpage_countpagination metadata onGET /references/{id}/updates. - Improved response times for
GET /referenceswheninclude_metadatais not requested.