MSC container and bill of lading tracking API

Use the MSC container and bill of lading tracking API to retrieve event records and reported status as structured JSON from MSC. Supply train number in the query; optionally select record type to set the requested scope. Use these results to review shipment milestones and organize delivery progress using the returned tracking events. For record type, choose auto / container / bl / booking. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
number
Optional parameters (6)
type
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. CSV and NDJSON exports are not supported; omit output or send json.
With output=csv|ndjson: the top-level list to turn into rows (e.g. `reviews`), or `.` for the whole object as one row.

Sample response

{
  "as_of": "Tracking results provided by MSC on 19.11.2026 at 13:20 Central Europe Standard Time",
  "cached": false,
  "credits_used": 1,
  "delivered": false,
  "destination": "SAINT LOUIS, US",
  "eta": "2026-12-31",
  "events": [
    {
      "date_raw": "08/11/2026",
      "description": "Empty to Shipper",
      "detail": [
        "EMPTY"
      ],
      "estimated": false,
      "facility": "MEDLOG (SHANGHAI) CO., LTD, TIANJING BRANCH",
      "facility_code": null,
      "location": "TIANJINXINGANG, CN",
      "time": "2026-11-08",
      "un_locode": "CNTXG",
      "vessel": null
    },
    {
      "date_raw": "12/11/2026",
      "description": "Export received at CY",
      "detail": [
        "LADEN"
      ],
      "estimated": false,
      "facility": "TIANJIN PORT PACIFIC INTERNATIONAL CONTAINER TERMINAL CO., LTD",
      "facility_code": "TPCT1",
      "location": "TIANJINXINGANG, CN",
      "time": "2026-11-12",
      "un_locode": "CNTXG",
      "vessel": null
    },
    {
      "date_raw": "12/11/2026",
      "description": "Export Return to Shipper",
      "detail": [
        "LADEN"
      ],
      "estimated": false,
      "facility": "TIANJIN PORT PACIFIC INTERNATIONAL CONTAINER TERMINAL CO., LTD",
      "facility_code": "TPCT1",
      "location": "TIANJINXINGANG, CN",
      "time": "2026-11-12",
      "un_locode": "CNTXG",
      "vessel": null
    },
    {
      "date_raw": "14/11/2026",
      "description": "Export back from shipper",
      "detail": [
        "LADEN"
      ],
      "estimated": false,
      "facility": "TIANJIN PORT PACIFIC INTERNATIONAL CONTAINER TERMINAL CO., LTD",
      "facility_code": "TPCT1",
      "location": "TIANJINXINGANG, CN",
      "time": "2026-11-14",
      "un_locode": "CNTXG",
      "vessel": null
    },
    {
      "date_raw": "30/11/2026",
      "description": "Estimated Time of Departure",
      "detail": [
        "MSC VENICE",
        "FY648A"
      ],
      "estimated": true,
      "facility": "TIANJIN PORT SECOND CONTAINER TERMINAL CO., LTD",
      "facility_code": "TSCT",
      "location": "TIANJINXINGANG, CN",
      "time": "2026-11-30",
      "un_locode": "CNTXG",
      "vessel": {
        "built": "2016",
        "flag": "LIBERIA",
        "imo": "9647473",
        "name": "MSC VENICE",
        "voyage": "FY648A"
      }
    },
    {
      "date_raw": "08/12/2026",
      "description": "Estimated Time of Arrival",
      "detail": [
        "MSC VENICE",
        "FY648A"
      ],
      "estimated": true,
      "facility": "GANGJI TERMINAL (PHASE IV)",
      "facility_code": "BLGAN",
      "location": "NINGBO, CN",
      "time": "2026-12-08",
      "un_locode": "CNNGB",
      "vessel": {
        "built": "2016",
        "flag": "LIBERIA",
        "imo": "9647473",
        "name": "MSC VENICE",
        "voyage": "FY648A"
      }
    },
    {
      "date_raw": "12/12/2026",
      "description": "Full Intended Transshipment",
      "detail": [
        "MSC VANDYA",
        "GO649N"
      ],
      "estimated": true,
      "facility": "GANGJI TERMINAL (PHASE IV)",
      "facility_code": "BLGAN",
      "location": "NINGBO, CN",
      "time": "2026-12-12",
      "un_locode": "CNNGB",
      "vessel": {
        "built": "2012",
        "flag": "PANAMA",
        "imo": "9484467",
        "name": "MSC VANDYA",
        "voyage": "GO649N"
      }
    },
    {
      "date_raw": "31/12/2026",
      "description": "Estimated Time of Arrival",
      "detail": [
        "MSC VANDYA",
        "GO649N"
      ],
      "estimated": true,
      "facility": "LONG BEACH PIER T TERMINAL",
      "facility_code": "Z952",
      "location": "LONG BEACH, US",
      "time": "2026-12-31",
      "un_locode": "USLGB",
      "vessel": {
        "built": "2012",
        "flag": "PANAMA",
        "imo": "9484467",
        "name": "MSC VANDYA",
        "voyage": "GO649N"
      }
    }
  ],
  "fetched_at": "2026-11-19T12:20:05.945Z",
  "number": "MSDU2377185",
  "origin": "TIANJINXINGANG, CN",
  "shipments": [
    {
      "bill_of_lading": null,
      "containers": [
        {
          "container_number": "MSDU2377185",
          "delivered": false,
          "eta": "2026-12-31",
          "events": [
            {
              "date_raw": "08/11/2026",
              "description": "Empty to Shipper",
              "detail": [
                "EMPTY"
              ],
              "estimated": false,
              "facility": "MEDLOG (SHANGHAI) CO., LTD, TIANJING BRANCH",
              "facility_code": null,
              "location": "TIANJINXINGANG, CN",
              "time": "2026-11-08",
              "un_locode": "CNTXG",
              "vessel": null
            },
            {
              "date_raw": "12/11/2026",
              "description": "Export received at CY",
              "detail": [
                "LADEN"
              ],
              "estimated": false,
              "facility": "TIANJIN PORT PACIFIC INTERNATIONAL CONTAINER TERMINAL CO., LTD",
              "facility_code": "TPCT1",
              "location": "TIANJINXINGANG, CN",
              "time": "2026-11-12",
              "un_locode": "CNTXG",
              "vessel": null
            },
            {
              "date_raw": "12/11/2026",
              "description": "Export Return to Shipper",
              "detail": [
                "LADEN"
              ],
              "estimated": false,
              "facility": "TIANJIN PORT PACIFIC INTERNATIONAL CONTAINER TERMINAL CO., LTD",
              "facility_code": "TPCT1",
              "location": "TIANJINXINGANG, CN",
              "time": "2026-11-12",
              "un_locode": "CNTXG",
              "vessel": null
            },
            {
              "date_raw": "14/11/2026",
              "description": "Export back from shipper",
              "detail": [
                "LADEN"
              ],
              "estimated": false,
              "facility": "TIANJIN PORT PACIFIC INTERNATIONAL CONTAINER TERMINAL CO., LTD",
              "facility_code": "TPCT1",
              "location": "TIANJINXINGANG, CN",
              "time": "2026-11-14",
              "un_locode": "CNTXG",
              "vessel": null
            },
            {
              "date_raw": "30/11/2026",
              "description": "Estimated Time of Departure",
              "detail": [
                "MSC VENICE",
                "FY648A"
              ],
              "estimated": true,
              "facility": "TIANJIN PORT SECOND CONTAINER TERMINAL CO., LTD",
              "facility_code": "TSCT",
              "location": "TIANJINXINGANG, CN",
              "time": "2026-11-30",
              "un_locode": "CNTXG",
              "vessel": {
                "built": "2016",
                "flag": "LIBERIA",
                "imo": "9647473",
                "name": "MSC VENICE",
                "voyage": "FY648A"
              }
            },
            {
              "date_raw": "08/12/2026",
              "description": "Estimated Time of Arrival",
              "detail": [
                "MSC VENICE",
                "FY648A"
              ],
              "estimated": true,
              "facility": "GANGJI TERMINAL (PHASE IV)",
              "facility_code": "BLGAN",
              "location": "NINGBO, CN",
              "time": "2026-12-08",
              "un_locode": "CNNGB",
              "vessel": {
                "built": "2016",
                "flag": "LIBERIA",
                "imo": "9647473",
                "name": "MSC VENICE",
                "voyage": "FY648A"
              }
            },
            {
              "date_raw": "12/12/2026",
              "description": "Full Intended Transshipment",
              "detail": [
                "MSC VANDYA",
                "GO649N"
              ],
              "estimated": true,
              "facility": "GANGJI TERMINAL (PHASE IV)",
              "facility_code": "BLGAN",
              "location": "NINGBO, CN",
              "time": "2026-12-12",
              "un_locode": "CNNGB",
              "vessel": {
                "built": "2012",
                "flag": "PANAMA",
                "imo": "9484467",
                "name": "MSC VANDYA",
                "voyage": "GO649N"
              }
            },
            {
              "date_raw": "31/12/2026",
              "description": "Estimated Time of Arrival",
              "detail": [
                "MSC VANDYA",
                "GO649N"
              ],
              "estimated": true,
              "facility": "LONG BEACH PIER T TERMINAL",
              "facility_code": "Z952",
              "location": "LONG BEACH, US",
              "time": "2026-12-31",
              "un_locode": "USLGB",
              "vessel": {
                "built": "2012",
                "flag": "PANAMA",
                "imo": "9484467",
                "name": "MSC VANDYA",
                "voyage": "GO649N"
              }
            }
          ],
          "latest_location": "TIANJINXINGANG, CN",
          "status": "Export back from shipper",
          "type": "20' DRY VAN"
        }
      ],
      "containers_count": 1,
      "delivered": false,
      "destination": "SAINT LOUIS, US",
      "eta": null,
      "origin": "TIANJINXINGANG, CN",
      "port_of_discharge": "LONG BEACH, US",
      "port_of_load": "TIANJINXINGANG, CN",
      "price_calculation_date": null,
      "transshipments": []
    }
  ],
  "status": "Export back from shipper",
  "tracking_type": "Container"
}

Response result

Response structure

Inferred from examples
  • as_ofstring
  • cachedboolean
  • credits_usedinteger
  • deliveredboolean
  • destinationstring
  • etastring
  • eventsobject[]
    • date_rawstring
    • descriptionstring
    • detailstring[]
    • estimatedboolean
    • facilitystring
    • facility_codenull | string
    • locationstring
    • timestring
    • un_locodestring
    • vesselnull | object
      • builtstring
      • flagstring
      • imostring
      • namestring
      • voyagestring
  • fetched_atstring
  • numberstring
  • originstring
  • shipmentsobject[]
    • bill_of_ladingnull
    • containersobject[]
      • container_numberstring
      • deliveredboolean
      • etastring
      • eventsobject[]
        • date_rawstring
        • descriptionstring
        • detailstring[]
        • estimatedboolean
        • facilitystring
        • facility_codenull | string
        • locationstring
        • timestring
        • un_locodestring
        • vesselnull | object
          • builtstring
          • flagstring
          • imostring
          • namestring
          • voyagestring
      • latest_locationstring
      • statusstring
      • typestring
    • containers_countinteger
    • deliveredboolean
    • destinationstring
    • etanull
    • originstring
    • port_of_dischargestring
    • port_of_loadstring
    • price_calculation_datenull
    • transshipmentsunknown[]
  • statusstring
  • tracking_typestring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use MSC container and bill of lading tracking API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.