---
title: "Event History of an Asset"
method: GET
path: "/skynet/asset/{id}/event/list"
tags: ["Tracking_Asset"]
---

# Event History of an Asset

`GET /skynet/asset/{id}/event/list`

## Query parameters

- `key` string, 32 character alphanumeric string, required
- `monitor_id` string
- `start_time` integer
- `end_time` integer
- `pn` integer
- `ps` integer

## Response `200`

OK

- DtoGetEventHisotryResp
  - `status` string — A string indicating the state of the response. On successful responses, the value will be Ok. Indicative error messages are returned for different errors. See the [API Error Codes](#api-error-codes) section below for more information.
  - `data` object — An object containing the information about the event history for the requested asset.
    - `list` DtoEvent[] — An array of objects with each object on the list representing one event.
      - `asset_id` string — ID of the asset. This is the same ID that was generated/provided at the time of creating the asset.
      - `event_type` 'enter' | 'exit' | 'speeding' | 'idle' — Nature of the event triggered by the asset. It can have following values: - enter: When the asset enters a specific geofence - exit: When the asset moves out of a specific geofence. - speeding: When the asset exceeds the certain speed limit. - idle: When the asset exhibits idle or no activity.
      - `geofence_id` string — ID of the geofence associated with the event.
      - `monitor_id` string — ID of the monitor associated with the event.
      - `monitor_tags` string[] — Tags associated with the monitor.
      - `prev_location` object — An object with details of the asset at the last tracked location before the event was triggered.
        - `location` object — prev_location information of the asset.
          - `lat` number — Latitude of the prev_location tracked for the asset.
          - `lon` number — Longitude of the prev_location tracked for the asset.
        - `timestamp` integer — A UNIX epoch timestamp in milliseconds representing the time at which the asset was at the prev_location.
        - `speed` number — If available, this property returns the speed of the asset, in meters per second, at the prev_location of the asset.
        - `bearing` number — If available, this property returns the heading of the asset from true north in clockwise direction, at the prev_location tracked for the asset.
        - `meta_data` object — Returns the custom data added during the location information upload.
      - `timestamp` integer — A UNIX epoch timestamp in milliseconds representing the time at which the event was added/created.
      - `triggered_location` object — An object with details of the asset at the location where the event was triggered.
        - `location` object — An object with information about the location at which the event was triggered.
          - `lat` number — Latitude of the triggered_location of the event.
          - `lon` number — Longitude of the triggered_location of the event.
        - `timestamp` integer — A UNIX epoch timestamp in milliseconds representing the time at which the asset was at the triggered_location.
        - `speed` number — If available, this property returns the speed of the asset, in meters per second, when the event was triggered.
        - `bearing` number — If available, this property returns the heading of the asset from true north in clockwise direction, when the event was triggered.
        - `meta_data` object — Returns the custom data added during the location information upload.
      - `triggered_timestamp` integer — A UNIX epoch timestamp in milliseconds representing the time at which the event was triggered.
      - `extra` object — Additional information about the event. Currently, this object returns the speed limit that was used to generate the over-speeding events, for a speeding type event. It is worth highlighting that, when the use_admin_speed_limit is true, the speed limit value will be obtained from the underlying road information. Whereas, if the use_admin_speed_limit is false, the speed limit will be equal to the customer_speed_limit value provided by the user when creating or updating the monitor.
    - `page` DtoPagination — An object with pagination details of the search results. Use this object to implement pagination in your application.
      - `total` integer — An integer value indicating the total number of items available in the data set. This parameter can be used to calculate the total number of pages available.
      - `page` integer — An integer value indicating the current page number (starting at 0).
      - `size` integer — An integer value indicating the maximum number of items retrieved per page.
      - `hasmore` boolean — A boolean value indicating whether there are more items available beyond the current page.
  - `message` string — Displays the error message in case of a failed request. If the request is successful, this field is not present in the response.

## Other responses

- `400` — Bad Request
- `500` — Internal Server Error

---

[API](https://skmtc.net/nextbillion-ai/apis/one-spec-service.md) · [All operations](https://skmtc.net/nextbillion-ai/apis/one-spec-service/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/nextbillion-ai/one-spec-service/revisions/b647f1808dda/schema)