GETNo key

Lanes with sailings

GETapi.navo24.com/v1/schedules/sailings/covered

Port pairs with upcoming sailings in our data, busiest first, with the number of sailings. Use it to know which lanes answer before you search.

Response schema

8 fields

Derived from the example response, nested as the JSON is.

okboolean

Whether the request succeeded.

dataobject

The payload. Everything an endpoint returns sits under this key.

lanesobject[]

lanes[]object

originstring

Origin code (airport IATA or UN/LOCODE).

destinationstring

Destination code (airport IATA or UN/LOCODE).

countnumber

How many cards the lane returned.

origin_namestring

Origin port name, falling back to its UN/LOCODE.

destination_namestring

Destination port name, falling back to its UN/LOCODE.

Errors

A failure on an open endpoint answers { "ok": false } with a human-readable message. Branch on the status code.

RATE_LIMITED429

Too many requests from one IP.

Try itNo key

curl 'https://api.navo24.com/v1/schedules/sailings/covered'

const res = await fetch("https://api.navo24.com/v1/schedules/sailings/covered");
const data = await res.json();

import requests

res = requests.get("https://api.navo24.com/v1/schedules/sailings/covered")
data = res.json()

Sample response example

{
  "ok": true,
  "data": {
    "lanes": [
      {
        "origin": "CNSHA",
        "destination": "SGSIN",
        "count": 1528,
        "origin_name": "Shanghai",
        "destination_name": "Singapore"
      },
      {
        "origin": "SGSIN",
        "destination": "CNSHA",
        "count": 1354,
        "origin_name": "Singapore",
        "destination_name": "Shanghai"
      }
    ]
  }
}

This preview uses documented example data and makes no live request.Get a key to run live.