Nearest ferry terminals, the lines that call there and their sailings per day

ferry_connections9 fields8 of these fields open in the demo

Source: Entur Journey Planner (timetables delivered to Entur; saved copy)
Geography: Around the address
Reported stale after: 14 days
Access: Requires an API key granted this section
Contract version: 1

Available with: trial key (open fields) · bought bundle or agreed plan (all fields) · Pricing

What this does not say

Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.

The five nearest ferry or boat terminals within 25 km, straight line in EPSG:25833 to the terminal's nearest quay, nearest first. Each lists the lines that call at it (at most 20, busiest first; line_count is the full number). Straight-line distance is not the road distance to the quay.
Each line carries sailings in the published timetable on three reference days: departures_weekday (a Tuesday, weekday_date), departures_saturday and departures_sunday. They are the whole line's service journeys in all directions and at all calls, not departures from this terminal, and they are the timetable as delivered to Entur, not what ran: cancellations, weather and demand-driven services are not in them. A reference day outside a service's season shows 0 and does not mean the line is discontinued.
carries_vehicles is true for car-ferry submodes (localCarFerry, nationalCarFerry, internationalCarFerry, highSpeedVehicleService); passenger boats and fast boats are listed with their submode. Only services that are published to Entur appear. Annual passenger and vehicle volumes per route are not served: Statens vegvesen's Ferjedatabanken needs credentials and offers no open export, and SSB's ferry table covers international traffic only.
Licence: NLOD 2.0 (Norsk lisens for offentlige data), Entur AS Journey Planner open API. Attribution: Entur AS and the listed operator or authority.

Fields

5 of 9 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” return values to anonymous callers; the rest require a key.

Field	Type	Role	Demo
stop_place_id	string \| null	context	open
terminal_name	string \| null	value	open
straight_line_distance_m	integer \| null (m)	value	open
latitude	number \| null	context	open
longitude	number \| null	context	open
line_count	integer \| null	value	open
car_ferry_line_count	integer \| null	value	open
lines	array<object> \| null	value	open
timetable_checked_at	string \| null	context	—

Fetch this section

Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.

curl --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643?include=ferry_connections'

# paginated, one section at a time
curl --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643/sections/ferry_connections?limit=25'

Try it now

This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.