Global Fishing Watch API
API v34Wings - Map Visualization

Get last report generated

Check status of the last report generated and download the data

Get the last report generated. This endpoint allows you to download the last report requested without generating it again. The endpoint only saves the last report for 30 minutes after its generation.

Get last report - Specifications

GET https://gateway.api.globalfishingwatch.org/v3/4wings/last-report

GET
/v3/4wings/last-report

Authorization

ApiKeyAuth
AuthorizationBearer <token>

In: header

curl -X GET "https://example.com/v3/4wings/last-report"
{  "entries": [    {      "callsign": "UBSS9",      "dataset": "public-global-vessel-identity:v3.0",      "date": "2022-01-13",      "detections": 12,      "entryTimestamp": "2022-01-14T14:00:00Z",      "exitTimestamp": "2022-01-14T16:00:00Z",      "firstTransmissionDate": "2019-07-12T12:08:27Z",      "flag": "ESP",      "geartype": "FISHING",      "hours": 26.6,      "imo": "8602866",      "lastTransmissionDate": "2025-03-01T23:55:50Z",      "lat": 49.33,      "lon": 141.15,      "mmsi": "273453380",      "shipName": "ALSEY",      "vesselIDs": 3,      "vesselId": "e6154b2e7-7762-4889-fb46-976ec72875e1",      "vesselType": "FISHING"    }  ],  "limit": 0,  "metadata": {},  "nextOffset": 0,  "offset": 0,  "total": 0}

Get last report - Responses

The endpoint can return 4 different responses depending of the last report status:

  • Report running. The report continues executing. It returns a json response with the info of the report running. Example:
{
  "uri": "/v3/4wings/report?format=JSON&datasets%5B0%5D=public-global-fishing-effort%3Av3.0&date-range=2023-12-31T00%3A00%3A00.000Z%2C2024-01-10T00%3A00%3A00.000Z&spatial-aggregation=true&temporal-resolution=ENTIRE&region-dataset=public-eez-areas&group-by=VESSEL_ID",
  "status": "running",
  "lastUpdate": "2024-02-05T13:34:06+0000"
}
  • Report finished correctly. In this case the response will be the same that the original request sent (See possibles responses of the report endpoint).
  • Report finished with error. In this case the response will be a json with the info of the error. Example:
{
  "message": {
    "statusCode": 422,
    "error": "Unprocessable Entity",
    "messages": [
      {
        "title": "region-id",
        "detail": "region-id query param is required"
      }
    ]
  },
  "status": 422
}
  • Report not found. In this case the endpoint return a 404 error. This can occurr because the last report response is only saved during 30 min after the report finished.

On this page