Ocean Freight Container Tracking Monitor (Multi-Carrier JSON)
Pricing
from $2.80 / 1,000 tracked reference delivereds
Ocean Freight Container Tracking Monitor (Multi-Carrier JSON)
Monitor ocean containers and bills of lading from Evergreen (ShipmentLink), COSCO and Matson in one normalized JSON schema: latest movement, vessel, voyage, location and ETA. Carrier auto-detected from the reference. Plain HTTP, no browser or proxies. Unknown references are logged, never billed.
Pricing
from $2.80 / 1,000 tracked reference delivereds
Rating
0.0
(0)
Developer
Steadfetch
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
1
Monthly active users
a day ago
Last modified
Categories
Features
Share
Ocean Container Tracking Scraper (Multi-Carrier JSON)
Tested daily. Last verified: 2026-10-30
Track ocean containers and bills of lading from Evergreen (ShipmentLink), COSCO and Matson through one normalized JSON schema. Give it a list of container or bill-of-lading numbers; it returns the latest public movement, vessel, voyage, location and ETA for each reference.
Universe & Coverage
- Universe: all ocean cargo containers and bills of lading trackable via the public APIs of shipping lines.
- Current coverage: 3 carriers, 16.6% of global container trade by TEU (source: Alphaliner Top 100, April 2026):
- Evergreen Line (ShipmentLink) - 5.8% TEU (#7 globally)
- COSCO - 10.6% TEU (#4 globally, largest Asian shipping line)
- Matson - 0.2% TEU (#30 globally, leader in Hawaii/Pacific routes)
- Total: 5,636,204 / 33,901,161 global TEU = 16.6%
- QA coverage: Evergreen and COSCO have live references in daily QA (DRYU9684015, 6468636830). Matson has no live reference yet (the source does not issue public IDs without an active shipment); it will be replaced when one is found.
- Future sources: Sinokor and Yang Ming are temporarily excluded because their Terms of Use prohibit automated scraping over plain HTTP. They will be re-evaluated if they switch to a public API without login.
- Excluded from current release: MSC (21.6% TEU, #1) and Maersk (13.7% TEU, #2) code exists but was not released (see PR #441). All top carriers use anti-bot protection (Akamai WAF, Oracle Apex SPA) requiring Playwright.
What it does
- Accepts container numbers (
4 letters + 7 digits, for exampleDRYU9684015) and numeric bill-of-lading numbers (for example6468636830). carrier: "auto"detects the likely carrier from the reference format and falls back through the other sources.- Returns one dataset item per reference with public data: normalized
events[]with ISO 8601 dates, pluscontainer/containersdetails for bills of lading. COSCO movement history is added tohistory[]when the source publishes it. - Plain HTTP, no browser and no proxies. All three sources answer from the platform egress.
- References without public data are logged and saved as run notes; they are not pushed to the dataset, so they are never billed.
Example output
{"url": "https://elines.coscoshipping.com/ebtracking/public/bill/containers/6468636830","scrapedAt": "2026-10-23T10:15:00.000Z","ref": "6468636830","refType": "bill_of_lading","carrier": "cosco","retrievedAt": "2026-10-23T10:15:00.000Z","containers": [{"number": "CSGU6362559","type": "40HQ","location": "TAN VU Terminal,Hai Phong,Hai Phong,Vietnam","label": "Loaded at First POL"}],"events": [{"at": "2026-10-22T06:30:00Z","status": "Loaded at First POL","location": "TAN VU Terminal,Hai Phong,Hai Phong,Vietnam"}]}
A COSCO bill of lading returns containers[] (one row per container) plus history[] with the movement list the public endpoint publishes.
Pricing
Pricing is 5 USD per 1,000 results (tracked references delivered) by pay per event (apify-default-dataset-item), plus the Apify-recommended apify-actor-start event at 0.00005 USD per run. A reference without data is never pushed and never charged. No proxies and no browser are required for the three sources.
Works on the Apify free plan: with the 5 USD monthly credit, about 999 tracked references can be delivered per month (N = floor((5.00 - 0.00005) / 0.005)).
Input
{ "refs": ["DRYU9684015", "6468636830"], "carrier": "auto" }
refs- container and/or bill-of-lading numbers (max 100 per run). Empty input falls back to the documented example bill of lading so the Store test always runs.carrier-auto(default),evergreen,coscoormatson.
FAQ
Which carriers are supported? Evergreen (ShipmentLink), COSCO (elines eBusiness) and Matson. Evergreen and COSCO have live public references in daily QA; Matson is reached through the public JSON endpoint its own tracking page uses (tracking_booking_proxy.php), which returns no data for a reference without an active shipment. MSC, Maersk, CMA CGM, ONE and Hapag-Lloyd are excluded - all use anti-bot protection (Akamai WAF, Oracle Apex SPA, captcha) requiring Playwright. Sinokor and Yang Ming are also excluded while their terms of use cannot be read over plain HTTP.
Does it need an API key or login? No. All sources are public and work without authentication.
Why is a reference missing from the dataset? Either the carrier has no public tracking data for it, or the format is not recognized. The run log and the ocean-container-tracking-monitor-notes key-value store list every reference without data and the reason.
Are dates in UTC? Evergreen publishes dates only (YYYY-MM-DD). COSCO and Matson publish a local date-time without an offset; it is normalized as YYYY-MM-DDTHH:MM:SSZ and should be read as source time.
Can it monitor changes? Not in v1. A watchlist/monitor mode (only new events) is a separate phase.
Maintenance
- Sources are validated against robots.txt, terms of use and cost in docs/legal-gate.md.
- Evergreen requires a descriptive User-Agent. The Actor never uses a search-engine or AI-bot User-Agent, because ShipmentLink's robots.txt disallows those named groups.
- The Actor is tested daily by Steadfetch QA against a live reference. If a source changes its HTML or JSON contract, the Actor is repaired before any new build.
- Matson sends a ~24 KB
Content-Security-Policyheader, above Node's 16 KB default. The Dockerfile and start scripts raise--max-http-header-sizeto 64 KB so the public page can be fetched.
Output schema
Dataset items are validated against .actor/dataset_schema.json before they are pushed. Unvalidated items never reach the dataset.