OOCL Cargo Tracking Scraper

What does OOCL Cargo Tracking Scraper do?

OOCL Cargo Tracking Scraper is an automated OOCL container tracking and shipment tracking API. Enter a container number, bill of lading number, or booking reference and receive structured cargo data covering shipment identifiers, release and customs status, containers, routes, vessels, ports, and the latest carrier event.

Use the Actor to track OOCL shipments in bulk, export carrier data to JSON, CSV, or Excel, and connect OOCL tracking results to logistics dashboards, transport management systems, alerts, schedules, and custom applications.

The Actor sends each submitted reference to the OOCL cargo tracking service, validates the response, and stores one dataset item for every successful shipment lookup. It supports:

• 📦 OOCL container tracking using container references
• 📄 OOCL bill of lading tracking for shipment visibility
• 🗂️ Booking number tracking from the same input field
• 🚢 Container routing and vessel data supplied by OOCL
• ✅ Cargo release and freight release status monitoring
• 🛃 Inbound customs and advanced manifest status collection
• 🔌 OOCL tracking API access through Apify
• ⏰ Scheduled cargo monitoring for recurring status checks

The scraper processes multiple references in parallel batches and retries temporary errors with proxy rotation when needed.

Why scrape OOCL shipment data?

Carrier websites are convenient for occasional checks but inefficient for operational shipment monitoring. Automated OOCL cargo tracking can help freight forwarders, importers, exporters, customs teams, logistics providers, and supply chain software companies:

• Check multiple OOCL shipments in a single run
• Monitor release, manifest, and customs clearance indicators
• Populate internal shipment records with structured carrier data
• Create customer-facing tracking dashboards
• Trigger notifications when the latest shipment event changes
• Schedule recurring container checks without manual work
• Export OOCL tracking data for auditing and analysis

What data can you extract from OOCL?

Data field	Description
tracking_number	Container, B/L, or booking reference submitted in the input
type	Reference or shipment type reported by OOCL
billOfLadingNumber	Bill of lading number associated with the shipment
bookingNumber	OOCL booking reference
cargoReleaseStatus	Cargo release status
freightChargeReleaseStatus	Freight-charge release status
inboundCustomsClearanceStatus	Inbound customs clearance indicator
advancedManifest	Advanced manifest information or status
containers	Containers associated with the tracked shipment
containerNumber	Individual container identifier
routing	Routing legs, ports, vessels, voyages, and schedule information
latestEvent	Latest event reported for the container

OOCL can return different fields depending on the reference type and shipment stage. The Actor keeps the complete data object so integrations do not lose carrier-specific details.

Ready-to-Run Examples

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

• Track OOCL Containers by Container Number — enter a container number and get its routing, release and customs statuses, container details, and latest event.

How to track OOCL shipments step by step

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

Example input

{
  "trackingNumbers": [
    "OOLU2748657830"
  ]
}

OOCL tracking input parameters

Parameter	Type	Required	Description
trackingNumbers	Array of strings	Yes	OOCL container, bill of lading, or booking references; one per line

OOCL Cargo Tracking Scraper output example

Each successful reference creates one dataset record. The example below is shortened and uses illustrative values:

{
  "tracking_number": "OOLU2748657830",
  "data": {
    "type": "CONTAINER",
    "billOfLadingNumber": "EXAMPLE-BL",
    "bookingNumber": "EXAMPLE-BOOKING",
    "cargoReleaseStatus": "AVAILABLE",
    "containers": [
      {
        "containerNumber": "OOLU2748657830",
        "latestEvent": {
          "location": "EXAMPLE PORT",
          "time": "2026-07-01T06:18:55Z",
          "event": "VESSEL DEPARTED"
        },
        "routing": {}
      }
    ]
  }
}

Actual status labels and nested routing fields come directly from OOCL and can vary by shipment. Unknown references are skipped and do not create a tracking-result charge event.

Integrations and OOCL tracking API

Apify provides the infrastructure required to use OOCL tracking data in production workflows:

• API access from Python, JavaScript, cURL, or any HTTP client
• Scheduled runs for recurring container and shipment monitoring
• Webhooks to trigger downstream automation when a run finishes
• Integrations with Google Sheets, Slack, Zapier, Make, and other services
• Dataset exports in JSON, CSV, Excel, XML, HTML, or RSS

Frequently asked questions

Is it legal to scrape OOCL?

The Actor retrieves shipment tracking information using references supplied by the user. Only query 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 OOCL.

Can I track multiple shipments at once?

Yes. Add multiple references to the input. The Actor processes them in parallel batches and saves one item per successful reference.

What types of tracking numbers are supported?

The Actor accepts container numbers, bill of lading numbers, and booking references through the same trackingNumbers input.

What if a tracking number is not found?

The Actor logs a warning, skips the reference, and does not create an empty output record or result charge.

How do I get support or report issues?

Open the Issues tab on the Actor page and include the Apify run ID and non-sensitive log context. Do not share API tokens or confidential documents.