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

Container Tracking API

Improvements

  • General: Enhance accuracy of port-specific coordinates
  • Port & terminal: Add Eurogate terminal vessel schedules ETAs to payloads

Bugs squashed

  • Wan Hai: Resolve connection disruption
  • PIL: Resolve connection disruption
  • Korea Marine Transport (KMTC): Add missing milestones to ensure better alignment with the carrier's tracking data

Container Tracking API

Bugs squashed

  • CMA: Resolve connection disruption
  • MSC: Resolve connection disruption
  • Yang Ming: Resolve connection disruption
  • Regional Container Lines: Resolve connection disruption

Container Tracking API

Bugs squashed

  • General: Hotfix to resolve ACI reference processing issue, and temporarily remove PIL from ACI carrier check

Container Tracking API

Improvements

  • COSCO: Track by booking support
  • Allow Container Trace endpoint to be used with simple tracking
  • New SeaLead supported carrier
  • Maersk: Improve inland destination logic
  • Add section to API reference for Vizion open API spec

Bugs squashed

  • CMA: Carrier returns "unknown" as vessel IMO in some payloads
  • Evergreen: Handle "-SMART" suffix added with track by booking number
  • OOCL: Resolve high rate of extraction failures

Standardizations

  • USCHS: Terminal event standardizations
  • SNKO: Standardized event mapping

Container Tracking API

Improvements

  • HHLA: Terminal events parsing improvements
  • CAMTR: Increase terminal event coverage

Bugs squashed

  • Evergreen: Resolve high track by booking failure rates

Standardizations

  • USCHS: Terminal event standardizations

Container Tracking API

Changes

  • General: Duplicate prevention now ignores the callback_url property; unique URLs cannot be used to create a duplicate reference

Improvements

  • General: Add unique milestone IDs and versions to milestone objects within reference updates

Bugs squashed

  • Heung-A: Resolve connection outage
  • PIL: Resolve connection outage

Standardizations

  • Hapag-Lloyd: Better standardization for transshipment events within HLCU references (including RTP journey codes related to DCSA)
  • Hapag-Lloyd: Map combined rail events to standardized rail milestones
  • Yang Ming: Event standardizations

Terminals

Improvements

  • General: Integrate with HHLA terminal schedules
  • CAMTR: Increase terminal coverage

Bugs squashed

  • USCHS: Address failiures due to large payloads

Standardizations

  • USCHS: Event standardizations

Container Tracking API

Improvements

  • Maersk: vessel identification improvements

Bugs squashed

  • Arkas: High rate of extraction failures
  • Pacific International Line: High rate of extraction failures

Standardizations

  • ZIM: event standardizations
  • Hyundai: location mappings

Container Tracking API

Improvements

  • Increase coverage at CAMTR

Bugs squashed

  • CMA: Container still in active shipment status randomly returning "no_data"
  • TS Line: Incorrect timestamp at POL
  • ONE Line: Different POD events can be standardized into similar or duplicated milestones in the update payload
  • ONE Line: Wrong description at transshipment port
  • MSC: Improved inland destination logic related to destination port override

Standardizations

  • USCHS: event standardizations
  • Arkas: event standardizations

Container Tracking API

Improvements

  • Improve Maersk vessel identification
  • General location data enhancements

Bugs Squashed

  • PIL: extraction failures
  • SITC: extraction failures
  • Crowley: extraction failures

Standardizations

  • USCHS event standardizations