Container Tracking API

Improvements

• General: Set an appropriate last update status that indicates a container was not found on a bill of lading or booking number (container_not_found_on_document)

Bugs squashed

• TS Line: Resolve connection outage
• ONE Line: Destination port incorrectly set to inland destination
• Wan Hai: Updated vessel legs logic causes legs to end too soon in some cases

Container Tracking API

Improvements

• Crowley: Track by booking

Bugs squashed

• Maersk: High number of extraction failures when tracking by bill of lading
• ONEY: Resolve connection outage
• Evergreen: Clean up "To be advised" string in vessel data

Container Tracking API

Bugs squashed

• TS Lines inferred bill of lading associated with old shipment
• OOCL: Resolve high number of extraction failures
• Evergreen: Resolve connection outage

Container Tracking API

Bugs squashed

• ONE Line: Adjust conflicting milestone standardizations based on true definitions of carrier's "eta" and "etb" datetimes

Container Tracking API

Features

• Introduction of Smart Updates tracking frequency optimizations

Container Tracking API

Features

• General: Add Marfret as a supported carrier

Improvements

• General: Internal enhancements to reduce event latency for Maersk and CMA

Bugs squashed

• PIL: Resolve connection issues

Container Tracking API

Bugs squashed

• Hapag Lloyd: Map "Arrival in" with mode of "waterway" to "Vessel arrived" milestone
• OOCL: Resolve high rate of extraction failures

Container Tracking API

Features

• General: OOCL Track by Booking support
• General: Auto Carrier Identification for bill of lading and booking numbers
• OOCL: Inland destination ETA added to update payloads when provided by carrier

Bugs squashed

• Hapag Lloyd: Fixed incorrect mapping of "Departure from" waterway milestone

Container Tracking API

Features

• General: ZIM track by booking support

Bugs squashed

• Hapag Lloyd: Resolved connection issue causing high rate of extraction failures
• Yang Ming: Resolved missing AIS milestones and ensured they are backfilled in affected payloads
• Sinokor: Resolved issue with transshipment port incorrectly set as destination port
• COSCO: Resolved references stuck in no_data status due to multiple BLs provided by carrier

Container Tracking API

Features

• General: Add Swire as a supported carrier

Improvements

• General: The Create Reference via ACI endpoint will focus on locating an active container journey with a supported carrier and, if no active journey exists, will return the most recent journey from a supported carrier
• Hapag-Lloyd: The Create Reference via Bill of Lading endpoint will automatically prepend MBL numbers with HLCU if not present in the subscription request
• TS Lines: The API will also strip TXZJ from MBL numbers (if provided) when attempting to locate relevant container data

Bugs squashed

• General: DCSA empty_indicator value behavior adjusted for better handling of "Gate in" milestones
• General: Resolve issue with duplicated milestones in update payloads
• Heung-A: Will correctly populate origin and destination port locations
• Sinokor: Will correctly populate origin and destination port locations
• SITC: Investigate and address elevated extraction failure rate
• Yang Ming: API will correctly extract DCSA events from the carrier and only fallback to non-DCSA if those events are unavailable