Route Planner API

Maritime RoutePlanner API

Calculate optimal sea routes between any two ports. Get precise distances, ETA predictions, ECA zone tracking, and canal crossings—all in one request.

Start Free TrialTry in Playground
10 Credits per Request
response.json
distance8,432 nm
duration17d 6h
crossingSuez, Malacca
pathPoints14 waypoints
Credits used10 credits
Global
Port Coverage
11
Gateways Supported
~300nm
Waypoint Spacing
10 Credits
Per Request

Popular Trade Routes

Click to explore route details. Our API calculates optimal paths through major canals and straits.

Route Analysis

From

Rotterdam

To

Singapore

8,432 nm

Total Distance

17 days

Est. Duration

Canals & Straits

SuezMalacca
Try This Route in Playground →

Complete API Response

Every request returns comprehensive route data including distance, duration, canal crossings, and waypoint coordinates for map visualization.

sample_response.json
{
  "routes": [
    {
      "fromPort": "NLRTM",
      "toPort": "SGSIN",
      "distance": {
        "distance": 8432,
        "unit": "kn"
      },
      "distanceInEca": {
        "distance": 120,
        "unit": "kn"
      },
      "crossing": [
        "Suez Canal",
        "Strait of Malacca"
      ],
      "estimatedArrival": "2026-05-18T14:30:00Z",
      "duration": {
        "years": 0,
        "month": 0,
        "days": 17,
        "hours": 6
      },
      "pathPoints": [
        [
          4.4792,
          51.9225
        ],
        [
          -5.6,
          35.9
        ],
        [
          32.3,
          30.6
        ],
        [
          103.8,
          1.3
        ]
      ]
    }
  ]
}
routesarray

One entry per consecutive port pair in your request. If you pass two ports, you get one route; if you pass five, you get four routes.

[ { fromPort, toPort, distance, ... }, ... ]
fromPort / toPortstring

UN/LOCODE pair describing this leg of the chain.

"fromPort": "NLRTM", "toPort": "SGSIN"
distanceobject

Total leg distance along the optimal sea path. The unit field mirrors the backend value (currently "kn").

{ "distance": 8432, "unit": "kn" }
distanceInEcaobject

Distance traveled within Emission Control Areas (ECAs) on this leg. Use for fuel planning and compliance.

{ "distance": 120, "unit": "kn" }
crossingarray

Canals and straits the leg passes through. Useful for understanding transit fees and restrictions.

["Suez Canal", "Strait of Malacca"]
estimatedArrivalstring

Calculated arrival time at toPort in ISO 8601 format, based on the departure time and vessel speed provided.

"2026-05-18T14:30:00Z"
durationobject

Leg duration broken down by time components for easy display.

{ "years": 0, "month": 0, "days": 17, "hours": 6 }
pathPointsarray

Array of [longitude, latitude] coordinates along the leg (GeoJSON order), sampled approximately every 300 nautical miles.

[[4.4792, 51.9225], [-5.6, 35.9], ...]

Route Waypoints for Map Visualization

The pathPoints array provides coordinate waypoints sampled approximately every 300 nautical miles along the calculated route. This spacing is optimized to:

  • Visualize routes accurately — enough points to show the actual path vessels take, including canal transits and strait crossings
  • Keep response sizes small — typically 10-30 waypoints per route instead of thousands of coordinates
  • Enable easy integration — use with Mapbox, Leaflet, Google Maps, or any mapping library to draw polylines

Example: Rotterdam to Singapore (8,432 nm)

14 waypoints•~600 nm average spacing•Includes Suez & Malacca transit points

What You Get

One API request, complete route intelligence

Distance

8,432 nm

Precise nautical miles via optimal path

ETA

17d 6h

Based on your specified speed

Crossings

2 canals

Suez Canal, Strait of Malacca

ECA Distance

120 nm

For emissions planning

11 Maritime Gateways

Route through or exclude any major canal or strait using the exclude_gateways parameter

🇪🇬suez

Suez Canal

Middle East

🇵🇦panama

Panama Canal

Americas

🇸🇬malacca

Strait of Malacca

Asia

🇩🇪kiel

Kiel Canal

Europe

🇮🇹messina

Strait of Messina

Europe

🇩🇰oresund

Oresund Strait

Europe

🇨🇱drake

Drake Passage

Americas

🇨🇱magellan

Strait of Magellan

Americas

❄️northeast

Northeast Passage

Arctic

❄️northwest

Northwest Passage

Arctic

🇬🇷corinth

Corinth Canal

Europe

Combine with Vessel Location for Real-Time ETAs

Get the vessel's current position, extract coordinates and speed, then calculate precise arrival predictions that update in real-time.

View Full Workflow

Location → Route → Precise ETA

FAQs

What ports are supported?

Any port worldwide using UN/LOCODE identifiers. Pass them in the ports parameter — a single comma-separated list of up to 5 codes (e.g., NLRTM,SGSIN for a single leg, or NOAKM,JPAIM,AEAJM for a 2-leg chain).

Can I plan a multi-port voyage in one call?

Yes. Pass up to 5 UN/LOCODEs to the ports parameter, separated by commas. The response will contain one entry in the routes array for each consecutive pair — so 3 ports gives you 2 routes, 5 ports gives you 4 routes.

How accurate is the ETA calculation?

estimatedArrival is calculated per leg using the vessel speed you provide and the optimal route distance, assuming constant speed. For real-time accuracy, combine with Vessel Location API data.

Can I exclude specific canals or straits?

Yes, use the exclude_gateways parameter with a comma-separated list of gateways to avoid (e.g., "suez,panama"). The API will calculate alternative routes.

What are ECA zones?

Emission Control Areas (ECAs) are designated maritime zones with stricter emission standards. Set eca=avoid to route around these zones for fuel planning purposes.

How are the pathPoints coordinates spaced?

Each leg's pathPoints array contains coordinates in [longitude, latitude] order (GeoJSON convention), sampled approximately every 300 nautical miles. This provides enough waypoints to visualize the route on a map while keeping the response size manageable.

Start Planning Maritime Routes

10 credits per request. Global port coverage. Up to 5 ports in a single chain.

Start Free TrialRead Documentation