Events of one IMO across MMSI changes. Each MMSI counts only while it reported this IMO (±10 min)

get/v1/vessels/imo/{imo}/events

Request

  • Base URL: https://api.aistrail.com
  • URL: https://api.aistrail.com/v1/vessels/imo/{imo}/events
  • Auth: HTTP bearer

Path parameters

imointeger required

Query parameters

fromstring date-time

ISO 8601 start; default: to minus 7 days

tostring date-time

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

typesstring

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

format'json' | 'csv' | 'xlsx'

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

limitinteger

Events per page, up to 10000 or the plan's rows per page when that is lower; default 1000

cursorstring

Opaque cursor from meta.next_cursor. When given, from, to and types are taken from the cursor

Response

Vessel events; each row carries its mmsi

Changes

No recorded changes to this operation across all 2 revisions of this API.