Events of one MMSI: port arrivals and departures, stops and moves, and changes of name, IMO, call sign, destination or draught
Computed from the archive when requested, ordered by time. Static changes are detected per source; the same change reported by several sources within an hour is listed once. A private vessel without access returns an empty page.
Request
- Base URL: https://api.aistrail.com
- URL: https://api.aistrail.com/v1/vessels/{mmsi}/events
- Auth: HTTP bearer
Path parameters
Query parameters
ISO 8601 start; default: to minus 7 days
ISO 8601 end (exclusive); default: now on plans with live data, otherwise now minus 24 h. Later values are clamped (see meta.embargo_cutoff). One query may span at most 31 days
all, or comma-separated event types: ENTER_ZONE, EXIT_ZONE, STATE_CHANGED, NAME_CHANGED, IMO_CHANGED, CALLSIGN_CHANGED, DESTINATION_CHANGED, DRAUGHT_CHANGED, AIS_GAP, ENCOUNTER, FLAG_CHANGED, POSITION_JUMP. Default: the first eight; the last four only when named or with all
json, csv (text/csv) or xlsx (Excel workbook); csv columns mmsi, imo, name, lat, lon, ts, event, old_value, new_value, port_id, port_locode, source, flag, sanctions, detail
Events per page, up to 10000 or the plan's rows per page when that is lower; default 1000
Opaque cursor from meta.next_cursor. When given, from, to and types are taken from the cursor
Response
Vessel events
Changes
No recorded changes to this operation across all 2 revisions of this API.