Skip to main content

Data sources

  • Ocean carriers (aka steamship lines): bill of lading/booking details, vessel ETA, containers, and milestones
  • Container terminal operators: container availability, last free day, holds, fees, and related terminal data
  • Container rail carriers: container milestones via rail
  • Vessel position data: vessel details and location tracking for accounts entitled to the vessel, routing, and map features (see Entitlements and Paid Features). Coverage and freshness vary by vessel and data source.

Supported ocean carriers

Coverage can vary by tracking-number type and source availability.
You can also use the Infer Tracking Number endpoint (Auto-Detect Carrier) to automatically identify the SCAC from a tracking number.

Ports and terminals

The Terminal49 API integrates with terminals at the following ports:
  • Baltimore
  • Boston
  • Charleston
  • Fraser Surrey (CA)
  • Halifax (CA)
  • Houston
  • Jacksonville
  • London Gateway (UK)
  • Long Beach
  • Los Angeles
  • Miami
  • Mobile
  • New Orleans
  • New York / New Jersey
  • Oakland
  • Philadelphia
  • Port Everglades
  • Portland
  • Prince Rupert (CA)
  • Savannah
  • Seattle
  • Southampton (UK)
  • Tacoma
  • Tampa
  • Vancouver (CA)
  • Virginia
The table below lists US terminals with their FIRMS codes. Terminal data availability can vary by field, terminal source, and shipment state.

Rail carriers

  • BNSF Railway
  • Canadian National Railway (CN)
  • Canadian Pacific Railway (CP)
  • CSX Transportation
  • Norfolk Southern Railway (NS)
  • Union Pacific Railroad (UP)

Known issues (ocean)

Shipment data is populated from requests to the shipping lines. Below is a list of known issues with the Terminal49 data sources:

CMA-CGM, APL, ANL

  • No container weight
  • No container seal number

Maersk, Sealand, Safmarine

  • Shipment departure/arrival events are not always available depending on when BL is entered into system.
  • No container seal number

Hamburg Süd

  • No estimated departure time
  • No container weight
  • No container seal number

MSC

  • No container seal number

Hapag Lloyd

  • No container weight
  • No container seal number

Evergreen

  • All dates are provided as dates, not datetimes. Terminal49 records and returns them all as midnight at the location the event happened (when location is available) or midnight UTC.
  • Only Dry, Reefer, and Flatpack container types are mapped to the Terminal49 system

COSCO

  • No departure or arrival events. Does not affect departure/arrival times.

OOCL

  • No container seal number

ONE

  • Only Dry and Reefer container types are mapped to the Terminal49 system

Yang-Ming

  • When BL has multiple containers, the container weight returned is the average of the shipment. (i.e. the BL gross weight / number of containers)

Hyundai Merchant Marine

  • No container type

ZIM

  • No container weight
  • No container seal number

Westwood Shipping

  • No container weight
  • Only Dry container types are mapped to the Terminal49 system

Data fields and availability

Below is a list of data that can be retrieved via the API, including whether it is always available, or whether it is only supported by certain carriers (Carrier Dependent), certain terminals (Terminal Dependent), or on certain types of journeys (Journey Dependent).

Shipment data

Shipment data is the primary data that comes from the carrier. It contains the details of the shipment retrieved from the Bill of Lading, and references multiple container objects.

Container data

At the container level, the following data is available. Container data is combined from all sources to create a single data view of the container. As such, some of this data will only be available when certain milestones have passed.

Milestone event data

When a milestone passes, the Terminal49 API will ping one of your webhooks with a Milestone event. For each milestone, the following data is always provided. Container, Shipment, Vessel, Location and Terminal data will be provided as objects that contain the information listed above.

Milestone events supported

A list of milestones that the API can track, as well as the event name used in the API. In future, further events may be supported.