CMA CGM Cargo Tracking Scraper

What does CMA CGM Cargo Tracking Scraper do?

CMA CGM Cargo Tracking Scraper is a bulk container tracking and shipment tracking API for CMA CGM cargo. Enter container numbers or bill of lading references and receive the complete CMA CGM tracking timeline as structured data, including shipment events, vessels, voyages, ports, facilities, and actual or estimated dates.

Use it to automate CMA CGM container tracking, monitor international shipments, build logistics dashboards, or connect carrier status data to your supply chain workflow. No coding is required: paste your references, click Start, and download the results as JSON, CSV, Excel, XML, or another dataset format.

The Actor checks CMA CGM shipment references in parallel and saves one dataset item for every reference that returns tracking data. It supports common logistics workflows such as:

• 📦 CMA CGM container tracking for individual containers or bulk reference lists
• 📄 Bill of lading tracking without manually checking each shipment
• 🚢 Vessel and voyage monitoring from the carrier event timeline
• 🌍 Port and facility tracking across origin, transshipment, and destination locations
• 🕒 Actual and estimated event dates for operational monitoring
• 🔌 CMA CGM tracking API integration through the Apify API
• ⏰ Scheduled shipment checks for recurring status updates

The scraper retries temporary failures and can rotate proxy IPs when the upstream tracking service limits or blocks a request.

Why scrape CMA CGM shipment data?

Checking containers one by one is slow when you manage many bookings, customers, or trade lanes. Structured CMA CGM cargo tracking data can help freight forwarders, importers, exporters, logistics platforms, and analysts:

• Keep transport management systems and customer portals current
• Detect newly reported shipment milestones
• Compare estimated and actual event times
• Monitor multiple CMA CGM containers in a single run
• Feed carrier events into dashboards, alerts, and exception workflows
• Export historical tracking snapshots for analysis and reporting

What data can you extract from CMA CGM?

Each result contains the submitted tracking number and the event objects returned by the CMA CGM tracking service.

Data field	Description
tracking_number	Container or B/L reference submitted in the input
eventType	Event category, such as transport or equipment activity
transportEventTypeCode	Carrier transport-event code when available
eventClassifierCode	Indicates whether the event is actual, estimated, or planned
eventDateTime	Date and time reported for the event
eventCreatedDateTime	Time the carrier created the event record
transportCall	Vessel, voyage, location, facility, and transport-call details
carrierSpecificData	CMA CGM-specific labels, phases, and internal location information
references	References associated with the event

Available fields can vary by shipment and event type. The Actor preserves the carrier response so downstream systems can use all available details.

Ready-to-Run Examples

Get started in seconds — open the example in the Apify Console and click Run:

• Track CMA CGM Containers by Container Number — enter a container number and get its full event timeline with vessels, ports, locations, and actual or estimated dates.

How to track CMA CGM shipments step by step

1. Open the Actor in Apify Console.
2. Add container or bill of lading references under Tracking Numbers, one per line.
3. Click Start.
4. Review the event timeline in the Output tab.
5. Download the dataset or retrieve it through the Apify API.

Example input

{
  "trackingNumbers": [
    "MAGU5661754"
  ]
}

CMA CGM tracking input parameters

Parameter	Type	Required	Description
trackingNumbers	Array of strings	Yes	CMA CGM container or bill of lading references; enter one per line

CMA CGM Cargo Tracking Scraper output example

One successful tracking reference produces one dataset item:

{
  "tracking_number": "MAGU5661754",
  "events": [
    {
      "eventType": "TRANSPORT",
      "eventClassifierCode": "ACT",
      "eventDateTime": "2026-07-01T06:18:55Z",
      "transportEventTypeCode": "ARRI",
      "transportCall": {
        "UNLocationCode": "TRMER",
        "modeOfTransport": "VESSEL"
      }
    }
  ]
}

The example is shortened. Actual results can contain additional references, vessel data, voyage numbers, facilities, locations, and carrier-specific fields. References with no tracking data are skipped and do not create a tracking-result charge event.

Integrations and CMA CGM tracking API

The Actor runs on the Apify platform, so CMA CGM tracking can be integrated into existing logistics systems without maintaining scraper infrastructure.

• API access — call the Actor from Python, JavaScript, cURL, or any HTTP client
• Schedules — run tracking checks hourly, daily, or at another interval
• Webhooks — notify a system when a run succeeds or fails
• Integrations — send results to Google Sheets, Slack, Zapier, Make, or other services
• Dataset exports — download JSON, CSV, Excel, XML, HTML, or RSS

Frequently asked questions

Is it legal to scrape CMA CGM?

The Actor retrieves shipment tracking information using references supplied by the user. Only track shipments you are authorized to access, and ensure your use complies with applicable laws and carrier terms. This Actor is independent and is not affiliated with or endorsed by CMA CGM.

Can I track multiple shipments at once?

Yes. Add multiple references to trackingNumbers; the Actor processes them in parallel batches.

What types of tracking numbers are supported?

The Actor accepts CMA CGM container numbers and bill of lading references. Enter each reference as a separate item.

What if a tracking number is not found?

The Actor logs a warning and skips that reference. It does not save an empty dataset item or create a result charge.

How do I get support or report issues?

Use the Issues tab on the Actor page and include the run ID, the type of reference used, and the relevant non-sensitive log lines. Do not post API tokens or confidential shipment information.