Home → Blog

A Rotterdam port congestion API returns port-call activity versus a 90-day baseline. On FreightPulse that is GET /api/v1/port-congestion?port=NLRTM with header X-API-Key. This is IMF PortWatch, lagged about 6–7 days — not live AIS wait times.

Free is 100 calls/mo (no card). Paid Basic is $49/mo (1,000 calls, 7-day trial on paid). MCP: mcp.freightpulsehq.com/mcp.

Request: Rotterdam (NLRTM)

curl -H "X-API-Key: YOUR_API_KEY" "https://freightpulsehq.com/api/v1/port-congestion?port=NLRTM"

Response: live FreightPulse (as_of 2026-09-25)

{
"success": true,
"data": {
"results": [
{
"port": "Rotterdam",
"locode": "NL RTM",
"country": "The Netherlands",
"congestion": "moderate",
"as_of": "2026-09-25",
"metrics": {
"recent_avg_portcalls_per_day": 87.1,
"baseline_avg_portcalls_per_day": 84.6,
"ratio_vs_baseline": 1.03
}
}
]
}
}

Do not reuse the USLAX 0.85 fixture. Do not quote a freight-rates USD fare as today’s price.

Go live

1. Register — Free 100 calls/mo.

2. Copy the X-API-Key when you subscribe.

3. GET /api/v1/port-congestion with port=NLRTM.

4. Read congestion, ratio_vs_baseline, and as_of.

Read Rotterdam congestion as JSON →