Environment

Vessel events (fishing, encounters, port visits, loitering)

Vessel activity events detected from AIS data. Types: fishing (apparent fishing activity), encounter (vessel-to-vessel meetings - potential transshipment), loitering (vessels stationary at sea), port_visit (arrivals and departures). Each event has position, duration, distances from shore/port, and EEZ/MPA/RFMO region data. Max date range: 366 days.

get/api/v1/gfw/events

Query parameters

vessel_idstring

GFW vessel ID (optional - omit for global events).

typestring

Event type: fishing, encounter, loitering, port_visit.

start_datestring

Start date (YYYY-MM-DD). Default: 90 days ago.

end_datestring

End date (YYYY-MM-DD). Default: today.

limitinteger

Max results.

Response

Vessel activity event records with positions, durations and region tags.

Example response

{
  "meta": {
    "endpoint": "/api/v1/fred/us/cpi",
    "data_time": "2026-04-16T14:30:00Z",
    "response_time": "2026-04-16T14:30:12Z",
    "provider": "Sugra API v1.0.1",
    "source": "sugra_crypto",
    "attribution": "Short interest and Reg SHO daily short volume data is owned by and sourced from FINRA (Financial Industry Regulatory Authority).",
    "fallback_chain": [
      "sugra_crypto",
      "sugra_finance"
    ]
  }
}

Changes

Changed in 2 of the 21 revisions of this API.1213

Aug 28, 2026560e8847c7b3121See the full diff
- ▲
  the response property data/count became optional for the status 200
  response-property-became-optional
- ▲
  the response property data/date_range became optional for the status 200
  response-property-became-optional
- ▲
  the response property data/event_type became optional for the status 200
  response-property-became-optional
- ▲
  the response property data/events became optional for the status 200
  response-property-became-optional
- ▲
  the response property data/total became optional for the status 200
  response-property-became-optional
- ▲
  response property data/count list-of-types was widened by adding types null and number to media type application/json of response 200
  response-property-list-of-types-widened
- ▲
  response property data/event_type list-of-types was widened by adding types null to media type application/json of response 200
  response-property-list-of-types-widened
- ▲
  response property data/events list-of-types was widened by adding types null to media type application/json of response 200
  response-property-list-of-types-widened
- ▲
  response property data/total list-of-types was widened by adding types null and number to media type application/json of response 200
  response-property-list-of-types-widened
- ▲
  the data/date_range response's property type/format changed from object/ to / for status 200
  response-property-type-changed
- ▲
  removed the required property data/date_range/end from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/date_range/start from the response with the 200 status
  response-required-property-removed
- ○
  added DateRange subschema #2 to the data/date_range response property anyOf list for the response status 200
  response-property-any-of-added
This revision also has 15 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 8, 20264c4530760ba112See the full diff
- ○
  added the optional property code to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property code to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property code to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property hint to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property hint to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property hint to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property plan to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property plan to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property plan to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property reason to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property reason to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property reason to the response with the 503 status
  response-optional-property-added

Full history