Vessel and voyage data API

Everything that starts with a hull or a trip. Who a vessel is, where it is now, where it has been, and what happened along the way.

This is the category to reach for when your question begins with a specific ship. If it begins with a place, you want Port & Trade or Domain & Fleet instead.

When to use it

You want to know	Start at
Who this vessel is, and its physical characteristics	Vessel Insights
Where it is now, or where it has been	Vessel Positions
Which vessels are inside an area right now	Vessel Positions
Which ports it has called at, and when	Voyage Insights
Whether it stopped reporting, met another ship, or reported a position that does not add up	Voyage Insights
Its inspection record	Voyage Insights
To be told when any of the above happens, without polling for it	Vessel Notifications

What is in it

Vessel Insights

Find a vessel by name, IMO, MMSI or attributes, then read its characteristics: type, class, tonnage, dimensions, flag and ownership.

Vessel Positions

Consolidated AIS positions: the latest fix for a set of vessels, the track one vessel took over a time window, or everything inside a circle or polygon.

Voyage Insights

Port calls, zone and port events, AIS reporting gaps, ship-to-ship pairings, positional discrepancies and port state control inspections.

Vessel Notifications

Subscribe to events for one vessel or a whole fleet, delivered by webhook, email digest or a pull request.

Paths you will call

Endpoints in this category sit under four path families, all on https://api.polestar-production.com:

Family	Holds
`/vessel-insights/v1/`	Vessel search and characteristics
`/meridia-voyage-intelligence/v1/`	Consolidated AIS positions
`/voyage-insights/v1/`	Everything that happened on a voyage
`/notifications/v1/vessels`	Vessel and fleet event subscriptions

Six different services answer the Voyage Insights family. That is invisible to you: one key, one host, one response envelope across all of them.

Vessel Positions sits behind /meridia-voyage-intelligence, the base path of the service that answers it. A prefix tells you which service answers a path, not which category a path belongs to.

A first call

Find a vessel, then ask what it has been doing.

Almost everything in Voyage Insights is keyed by IMO, so a search is usually step one.

Positions are the exception in shape. Both position endpoints are POST, because the filter is a JSON body rather than a query string:

They read; they create nothing. Swap imo_numbers for a geographic_filter holding a circle or a polygon to ask the same question about an area instead of a hull.

Gaps and pairings are signals, not verdicts

An AIS reporting gap means a vessel stopped transmitting. It does not tell you why: equipment fails, and satellite coverage is imperfect. Treat these endpoints as inputs to your own risk model, not as findings. Concepts & Terminology explains what each event asserts.

Concepts & Terminology

What a voyage, a port call and an AIS gap mean.

Notifications & Webhooks

Subscribing once instead of polling.

Vessel Types

The type and class vocabulary used in search filters.

Vessel & Voyage

When to use it#

What is in it#

Paths you will call#

A first call#

Related#

When to use it

What is in it

Paths you will call

A first call

Related