# Container Tracking API, Portcast Predictive ETA and Vessels (`nabeelbaghoor/container-tracking-predictive-eta-api`) Actor

Read ocean container tracking from your Portcast account: predicted and carrier ETAs, milestones, AIS vessel position, container route, delay risks, terminal last free day and holds, vessel tracking, port congestion, sailing schedules and 100+ carrier SCACs. Read only. Bring your own key.

- **URL**: https://apify.com/nabeelbaghoor/container-tracking-predictive-eta-api.md
- **Developed by:** [Nabeel Hassan](https://apify.com/nabeelbaghoor) (community)
- **Categories:** Developer tools, Business, Travel
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $15.00 / 1,000 tracked container returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Container Tracking API for Portcast: Predictive ETA, Milestones and Vessels

Read the ocean containers tracked in your Portcast account through the Portcast API with your own API key, as clean dataset rows: Portcast predicted ETAs next to carrier ETAs, milestones, AIS vessel positions, routes, delay risks, terminal data, port congestion and sailing schedules.

Portcast is a Singapore based container visibility platform that tracks containers across 100+ ocean carriers and NVOCCs, enriches carrier milestones with AIS vessel data and 70+ other sources, and predicts arrival times with its own machine learning model. This actor wraps the read only part of its documented API on api.portcast.io, so you can pull predicted ETAs into Google Sheets, BI dashboards, ERP or TMS systems, exception alerts or AI agents without writing a client. Bring your own API key.

BYOK, not live tested: every route, parameter and field comes from Portcast's published OpenAPI definitions on portcast.stoplight.io (Container Tracking, Vessel Tracking, Port Congestion and Sailing Schedules APIs), checked on 2026-10-26. The routes were probed with an invalid key on the same day. The actor has not been run against a live Portcast key.

### What it does

- **Container tracking and predicted ETA**: one row per tracked container (Portcast Bill of Lading Bookmark) with container number, bill of lading or booking number, carrier SCAC, tracking status code, port of loading and port of discharge (UN/LOCODE and name), carrier scheduled, Portcast predicted and actual arrival at the port of discharge, actual departure from the port of loading, POD terminal, the final vessel with its IMO and latest AIS position, and the latest milestone. The full Portcast record (every leg, delay reasons, transport plan, CO2 emissions, container size and type) is kept in `attributes`.
- **Container milestone events**: one row per standardized milestone (empty pick up, gate in, loaded, departure, transshipment, arrival, unload, gate out, delivered, empty return) with actual and estimated times, port, location type, vessel, voyage and terminal.
- **Container route and vessel position**: the actual AIS path and the optimal route for each leg, plus the vessel the container is on now with its latest latitude, longitude, speed and course.
- **Container risks**: active risks per container, such as predicted delay at arrival or departure, port congestion on route, possible rollover, weather events and vessel not attributed.
- **Container terminal data**: export terminal gate in, earliest receiving dates and cut offs, and import terminal discharge, holds, last free day, demurrage owed, pickup appointment, yard location and gate out (a Portcast add-on).
- **Vessel tracking**: Portcast vessel bookmarks with origin and target port, scheduled, predicted and actual arrival and voyage details.
- **Port congestion**: weekly congestion category with vessel waiting and dwell time percentiles, or daily vessels berthed, waiting at anchorage and total waiting time, for any UN/LOCODE.
- **Sailing schedules**: scheduled sailings between two ports with carrier, legs, vessels, voyages, service routes, terminals and transit time.
- **Supported carriers**: every carrier SCAC Portcast covers, with SCAC synonyms, bill of lading prefixes and supported upload types.
- **Numbers just work**: in the route, risk and terminal modes, give container or bill of lading numbers and the actor finds their bookmark IDs first, without charging for that lookup.
- **Pay only for results**: unknown numbers, empty lists and refused lookups are recorded as a free row that says why, never charged.

### How to use it

1. Sign in to the Portcast web app and open your profile page (app.portcast.io/profile); your organisation API key is there.
2. Paste the key into the API key field (or set the DATA_API_KEY secret). It is sent only to api.portcast.io in the `x-api-key` header and is removed from everything the actor logs.
3. Pick a mode, add container numbers, bill of lading numbers, bookmark IDs or ports, and start the run. Download the rows as JSON, CSV or Excel, or call the actor from your own code or a schedule.

Containers must already be tracked in your Portcast account (uploaded through its web app or API). This actor never uploads containers, bookings or vessels, because Portcast bills each new Bookmark ID and a repeated run would create duplicates. Reading tracking data is not billed by Portcast.

A missing or rejected key, or an account without the Port congestion API, ends the run cleanly with a status message that says what to change.

### Input

| Field | Modes | Description |
| --- | --- | --- |
| `mode` | all | `containers` (default), `containerEvents`, `containerRoute`, `containerRisks`, `terminalData`, `vesselTracking`, `portCongestion`, `sailingSchedules` or `carriers` |
| `containerNumbers` | Container modes | ISO 6346 container numbers already tracked in Portcast |
| `billOfLadingNumbers` | Container modes | Bill of lading or booking numbers; every tracked container under each is returned |
| `bookmarkIds` | Container modes | Portcast Bill of Lading Bookmark IDs, read directly |
| `carrierScac` | Container modes | One carrier SCAC to narrow lookups or the full listing |
| `enterpriseCustomer` | Container modes | Enterprise accounts only: the customer organisation to read (x-customer header) |
| `vesselBookmarkIds` | Vessel tracking | Portcast Vessel Bookmark IDs |
| `portCodes`, `congestionSeries` | Port congestion | UN/LOCODEs, and weekly or daily series |
| `dateFrom`, `dateTo` | Port congestion, Sailing schedules | YYYY-MM-DD window |
| `originPort`, `destinationPort` | Sailing schedules | Origin and destination UN/LOCODEs (required) |
| `sailingDateBasis`, `sailingCarriers`, `transshipments`, `nearbyOrigins`, `nearbyDestinations` | Sailing schedules | Dates by departure or arrival, carriers, 0, 1 or 2 transshipments, nearby ports |
| `maxResults` | all | Most rows to return and charge for |
| `requestsPerMinute` | all | Pacing for calls to Portcast |
| `apiKey` | all | Your Portcast API key (secret) |

### Output

Every row has flat columns that are easy to filter: `bookmarkId`, `containerNumber`, `billOfLading`, `carrierScac`, `trackingStatus`, `polLocode`, `polName`, `podLocode`, `podName`, `podPredictedArrival`, `podScheduledArrival`, `podActualArrival`, `polActualDeparture`, `vesselName`, `vesselImo`, `event`, `eventCode`, `eventTime`, `eventEstimatedTime`, `locationLocode`, `locationName`, `terminalName`, `lastFreeDay`, `latitude`, `longitude`, `riskCode`, `date`, `congestionCategory`, `transitTime`, `name` and `code`. The full Portcast record is kept in `attributes`. Port times are local time at the port, as Portcast reports them. A refused or empty lookup has `found` set to false and a `note` with Portcast's own words.

Example container row (identifiers, ports, vessel and position from the Portcast API reference examples; the times are illustrative):

```json
{
    "mode": "containers",
    "modeLabel": "Container tracking",
    "recordType": "container",
    "query": "TLLU1181321",
    "found": true,
    "id": "da420d2e-7657-4b2b-80a9-a6a30e58482c",
    "bookmarkId": "da420d2e-7657-4b2b-80a9-a6a30e58482c",
    "containerNumber": "TLLU1181321",
    "billOfLading": "ONEYANRB31646600",
    "carrierScac": "ONEY",
    "trackingStatus": "JOURNEY_IN_PROGRESS",
    "polLocode": "USORF",
    "polName": "NORFOLK",
    "podLocode": "GHTEM",
    "podName": "TEMA",
    "podPredictedArrival": "2026-05-02T06:00:00",
    "podScheduledArrival": "2026-05-04T08:00:00",
    "podActualArrival": null,
    "polActualDeparture": "2026-04-09T21:30:00",
    "vesselName": "MAERSK PUELO",
    "vesselImo": "9306172",
    "event": "Departure",
    "eventCode": "DEPART",
    "eventTime": "2026-04-09T21:30:00",
    "locationLocode": "USORF",
    "locationName": "NORFOLK",
    "terminalName": "MERIDIAN PORT SERVICE LIMITED",
    "latitude": 26.527666,
    "longitude": -78.766,
    "attributes": { "bill_of_lading": { "...": "..." }, "container_event_list": [], "sailing_info_tracking": [], "delay_lists": [], "co2_emissions": {} },
    "retrievedAt": "2026-10-26T12:00:00.000Z",
    "note": null
}
```

Milestone rows carry `event`, `eventCode` (PICKUP, GATEIN, LOAD, DEPART, ARRIVE, UNLOAD, GATEOUT, DELIVER, RETURN and more), `eventTime`, `eventEstimatedTime`, `locationLocode`, `code` (POR, POL, POT, POD or POA) and the carrier's own wording in `name`. Route rows carry the current vessel with `latitude` and `longitude`. Risk rows carry `riskCode` and its description in `name`. Congestion rows carry `date`, `congestionCategory` and the waiting and dwell time measures in `attributes`.

### Pricing

| Event | Price | Charged for |
| --- | --- | --- |
| `container-tracking` | 0.015 USD | Each tracked container with its journey and predicted ETA |
| `container-event` | 0.005 USD | Each container milestone |
| `container-route` | 0.01 USD | Each container route with the current vessel position |
| `container-risk` | 0.005 USD | Each active container risk |
| `terminal-data` | 0.01 USD | Each container's export and import terminal data |
| `vessel-tracking` | 0.01 USD | Each vessel bookmark |
| `port-congestion-metric` | 0.005 USD | Each weekly or daily congestion record |
| `sailing-schedule` | 0.005 USD | Each scheduled sailing |
| `carrier` | 0.005 USD | Each supported carrier |

Unknown numbers, empty lists, refused lookups and the number to bookmark ID lookup are never charged. Your Portcast plan is billed separately by Portcast.

### FAQ

#### What is the Portcast API?

Portcast is a container visibility and predictive ETA platform. Its API on api.portcast.io tracks containers by carrier SCAC plus container, booking or bill of lading number; each tracked container gets a Bookmark ID, and from then on Portcast refreshes its milestones, vessel positions and predicted arrival at least twice a day.

#### Do I need my own Portcast API key?

Yes. This is a bring your own key actor: it calls Portcast with your organisation key, under your plan and its terms. The key is on your profile page in the Portcast web app; if you have no web app access, Portcast sales can set up an account.

#### Does this actor cost me Portcast tracking credits?

No. Portcast bills per Bookmark ID created by an upload, and its FAQ says reads are not limited. This actor only reads containers you already track; it never uploads a container, booking or vessel.

#### How do I get the predicted ETA of a container?

Run Container tracking with the container number or bill of lading number. `podPredictedArrival` is Portcast's machine learning prediction for arrival at the port of discharge, `podScheduledArrival` is the carrier's schedule and `podActualArrival` fills in once the vessel arrives. Every leg's predictions are in `attributes.sailing_info_tracking`.

#### Where does the vessel position come from?

From AIS data Portcast attaches to each leg. Container tracking returns the final vessel's latest position; Container route returns the vessel the container is on now with its latest AIS fix, plus the actual and optimal route.

#### What do the terminal data and risk modes need?

Container terminal data is a Portcast add-on (ask support@portcast.io to enable it); without it Portcast refuses each container and the actor records a free row that says so. Container risks returns only ongoing or future risks such as predicted delays, port congestion on route, rollover and weather.

#### Can I get port congestion and sailing schedules without tracking anything?

Yes, if your plan includes them. Port congestion takes any UN/LOCODE; Sailing schedules searches the top carriers' schedules between two ports. An account without the Port congestion API ends the run with Portcast's own message.

#### What are the rate limits?

Portcast sets no limit on reads but asks to be told about unusually high volumes. The actor paces itself at 60 requests per minute by default and honours Retry-After on a 429.

### Keyword map

container tracking API, predictive ETA API, ocean container tracking, container ETA prediction, bill of lading tracking, booking number tracking, container milestones API, vessel tracking API, AIS vessel position, container route map, shipment delay risk, rollover detection, terminal last free day, demurrage and holds, port congestion API, vessel waiting time, sailing schedules API, carrier SCAC list, NVOCC tracking, Portcast API, Portcast container tracking, Portcast predicted ETA.

### Routes and verification

Wrapped routes on https://api.portcast.io/api/v2: `/eta/tracking/bill-of-lading-bookmarks`, `/eta/tracking/bill-of-lading-bookmarks/{bookmark_id}`, `/eta/tracking/bill-of-lading-bookmarks/{bookmark_id}/container_route`, `/eta/tracking/bill-of-lading-bookmarks/{bookmark_id}/risks`, `/eta/tracking/bill-of-lading-bookmarks/{bookmark_id}/import_export_plan`, `/eta/tracking/vessel-bookmarks/{vessel_bookmark_id}`, `/port-congestion`, `/eta/sailing_schedules` (a POST search that creates nothing) and `/eta/scac`. All were probed twice on 2026-10-26 with a deliberately invalid key and answered Portcast's 401 `{"Error": "Not authorized"}`, while invented paths answered a 404 saying the URL was not found, so every route above exists as documented. Response shapes, filters and fields are taken from the vendor's OpenAPI definitions, not from live data.

### Licensing and data use

This actor works only with your own Portcast account and API key, and Portcast's terms apply to everything it returns. Those terms limit the data to your internal business use and forbid reselling it. This actor is not affiliated with or endorsed by Portcast.

# Actor input Schema

## `mode` (type: `string`):

Container tracking: one row per tracked container with carrier, ports, scheduled, Portcast predicted and actual ETA, vessel and AIS position. Container milestone events: one row per milestone. Container route, Container risks and Container terminal data read the add-on APIs for each container. Vessel tracking reads vessel bookmarks. Port congestion and Sailing schedules work on ports. Supported carriers lists every carrier SCAC. This actor never uploads containers, so it never creates a billable Portcast bookmark.

## `containerNumbers` (type: `array`):

Container modes, optional. One ISO 6346 container number per line. It must already be tracked in your Portcast account; this actor never starts tracking. Leave all three container inputs empty in Container tracking to list every tracked container.

## `billOfLadingNumbers` (type: `array`):

Container modes, optional. One bill of lading or booking number per line; every tracked container under it is returned.

## `bookmarkIds` (type: `array`):

Container modes, optional. One Portcast Bill of Lading Bookmark ID per line, read directly.

## `carrierScac` (type: `string`):

Container modes, optional. One carrier SCAC such as CMDU or MSCU; narrows the container and bill of lading lookups, or the full listing, to that carrier.

## `enterpriseCustomer` (type: `string`):

Container modes, optional, for Portcast enterprise accounts only. The customer name that says which organisation to read tracking data from (sent as the x-customer header).

## `vesselBookmarkIds` (type: `array`):

Vessel tracking only. One Portcast Vessel Bookmark ID per line, as the Portcast web app or a vessel upload gives it.

## `portCodes` (type: `array`):

Port congestion only. One port UN/LOCODE per line.

## `congestionSeries` (type: `string`):

Port congestion only. Which of the two series Portcast returns to put one row each.

## `dateFrom` (type: `string`):

Port congestion and Sailing schedules, optional. YYYY-MM-DD. Congestion defaults to 60 days ago; sailings depart (or arrive) on or after it.

## `dateTo` (type: `string`):

Port congestion and Sailing schedules, optional. YYYY-MM-DD. Congestion defaults to today; sailings depart (or arrive) on or before it.

## `originPort` (type: `string`):

Sailing schedules, required there. Origin port UN/LOCODE, for example NLRTM.

## `destinationPort` (type: `string`):

Sailing schedules, required there. Destination port UN/LOCODE, for example CNSHA.

## `sailingDateBasis` (type: `string`):

Sailing schedules only. Whether Date from and Date to bound the departure or the arrival of each sailing.

## `sailingCarriers` (type: `array`):

Sailing schedules, optional. Carrier SCACs to include; leave empty for every covered carrier.

## `transshipments` (type: `array`):

Sailing schedules, optional. Keeps sailings with these transshipment counts; leave empty for all.

## `nearbyOrigins` (type: `boolean`):

Sailing schedules only. Also returns sailings from ports near the origin port.

## `nearbyDestinations` (type: `boolean`):

Sailing schedules only. Also returns sailings to ports near the destination port.

## `maxResults` (type: `integer`):

The most rows this run returns and charges for.

## `requestsPerMinute` (type: `integer`):

Pacing for calls to the Portcast API. Portcast sets no limit on reads, but asks to be told about unusually high volumes.

## `apiKey` (type: `string`):

Your own Portcast organisation API key from the profile page of the Portcast web app (app.portcast.io/profile). Stored as a secret and sent only to api.portcast.io in the x-api-key header; it is never logged. You can instead set the DATA_API_KEY environment secret.

## Actor input object example

```json
{
  "mode": "containers",
  "congestionSeries": "weekly",
  "sailingDateBasis": "departure",
  "nearbyOrigins": false,
  "nearbyDestinations": false,
  "maxResults": 100,
  "requestsPerMinute": 60
}
```

# Actor output Schema

## `records` (type: `string`):

One row per container, milestone event, route, risk, terminal record, vessel, congestion metric, sailing or carrier.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("nabeelbaghoor/container-tracking-predictive-eta-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("nabeelbaghoor/container-tracking-predictive-eta-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call nabeelbaghoor/container-tracking-predictive-eta-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nabeelbaghoor/container-tracking-predictive-eta-api"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/U7JKd6RRRGw2EP17S/builds/ScAJ9BYGGfcfEyfiz/openapi.json
