Data coverage

Terminal49 is a single Automated Container Tracking API for bills of lading, bookings, and container numbers. Behind it are direct integrations with ocean carriers, port terminal operators, and North American rail carriers, plus AIS vessel data — normalized into one data model so you integrate once and get every source. This section lists exactly what is live in production, so you can verify coverage for your lanes before you write a line of code. Coverage reflects production as of 14 August 2026; the coverage changelog records additions and removals. Use GET /shipping_lines for the current carrier list on your account.

​

Data sources

• Ocean carriers (shipping lines / VOCCs): bill of lading and booking details, vessel ETAs, containers, and transport milestones. See ocean carriers.
• Ports & terminals: global mapping of origin, destination, transshipment, and inland locations on every route, plus availability, last free day (LFD), holds, and fees straight from the terminal operator. See ports & terminals.
• Rail carriers: inland rail milestones across North America. See rail carriers.
• Vessels: identity on the voyage, plus AIS position and projected route. See vessels.

​

Supported ocean carriers

Terminal49 integrates directly with each supported shipping line and normalizes their data into a single API. Filter by name, Standard Carrier Alpha Code (SCAC), or the number types you can send on a tracking request.

​

Account-enabled carriers

Some carriers are live in production but not in the public default set. Contact Terminal49 to enable them on your account. See account-enabled carriers for Seaboard Marine (SMLU) and Trailer Bridge (TRBR).

​

Supported terminals

Terminal49 maps origin, destination, transshipment, and inland ports and terminals globally on every route, and attributes carrier events — arrival, departure, loaded, discharged, transshipment — to the location where they occur. Direct terminal integrations add the operational answers on top: availability, holds, fees, and last free day, straight from the terminal operator.

​

Rail carriers

Tracking continues inland: North American rail milestones, rail ETA, and rail LFD arrive on the same container objects, covering all six Class I railroads — BNSF, CN, CP, CSX, Norfolk Southern, and Union Pacific.

​

Known issues (ocean)

Shipment data comes from the carrier, and some carriers do not publish every field. The gaps we see most often — missing seal numbers, weights, or equipment types — are listed on the ocean carriers page.

​

Data fields and availability

The tables on field availability describe the fields you can retrieve, and whether a field is always present, carrier-dependent, terminal-dependent, or journey-dependent (for example inland rail).

​

Shipment data

Shipment data comes from the carrier. It contains the bill of lading details and references the related containers. See shipment fields.

​

Container data

Container data is combined from every source into one view. Some fields appear only after a milestone has passed. See container fields.

​

Milestone event data

When a milestone passes, Terminal49 can send a webhook. See milestone fields and the webhook event catalog.

​

Milestone events supported

The full milestone list — vessel, terminal, rail, transshipment, and inland — is on field availability.