Port and expected ships

GET https://api.api.sh/vessels/v1/port
1 credit / call travel & events try it in the playground →

A port by UN/LOCODE: name, country, and its expected ships, recent arrivals, departures and ships in port as the site shows them publicly (time, ship type, flag, year built, GT, DWT and size; ship names and some columns are subscriber-only and come back null).

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
idrequired string UN/LOCODE of the port (e.g. NLRTM Rotterdam, SGSIN Singapore, USLAX Los Angeles), or the site's port id such as NLRTM001. Example: NLRTM
limit integer Rows per list (default 50, max 100).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/vessels/v1/port?id=NLRTM" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.