v1

latestOpenAPI 3.0.1Apache 2.02026-08-063494581.6 MB
esper_cloud_api_AndroidDevice

Download Event Feed for Device

Download the event feed for an Android device. Retrieves a paginated, chronologically ordered list of EventFeed records for the specified Android device, each containing an event id, message_id, device_status_id, created_on timestamp, and a message describing what occurred — including commands issued, who issued them, and from which state they were issued. Results default to 250 records per page.

This endpoint is for Android devices only. For group-level event history, use GET /enterprise/{enterprise_id}/group/{group_id}/download/eventfeed/ instead.

About the Event Feed

The event feed is a chronological record of activity on a device, capturing commands, state transitions, and other significant events. It is the primary source for auditing device history, investigating incidents, and understanding the sequence of operations performed on a device. Each event links back to a device_status_id, which can be used to retrieve the full telemetry snapshot associated with that event. Available query parameters:

limit — number of results per page (default: 250) offset — pagination offset (default: 0)

Common Use Cases

Auditing the full history of commands issued to a specific Android device, investigating device incidents by reviewing the sequence of events leading up to a failure or unexpected state change, downloading a complete event log for offline analysis or compliance reporting, and correlating device events with command requests to verify that operations were executed as expected.

Best Practices

For large event histories, use limit and offset to paginate through results rather than fetching everything in a single call. If you only need the most recent device status snapshot rather than a full event history, use GET /enterprise/{enterprise_id}/device/{device_id}/status/?latest_event=1 instead — it is significantly lighter. For the Esper Console timeline view of device events, use GET /v1/enterprise/{enterprise_id}/device/{device_id}/report/eventfeed/ instead, which returns the same data with a smaller default page size suited to UI rendering.

Workflow

  1. Call GET /enterprise/{enterprise_id}/device/{device_id}/ to confirm the device details and retrieve the device_id.
  2. Call this endpoint to retrieve the full chronological event feed for the device.
  3. Use message and created_on to identify the events relevant to your investigation or audit.
  4. Use device_status_id from a specific event to retrieve the associated telemetry snapshot via GET /enterprise/{enterprise_id}/device/{device_id}/status/ if deeper context is needed.
get/enterprise/{enterprise_id}/device/{device_id}/download/eventfeed/

Path parameters

enterprise_idstring required

A UUID string identifying this enterprise.

device_idstring required

A UUID string identifying the device

Query parameters

limitinteger

Number of results to return per page.

offsetinteger

Return results from this index.

Response

successful operation

countinteger required
nextstring url nullable
previousstring url nullable

Example response

{
  "results": [
    {
      "device": "https://{example}-api.esper.cloud/api/enterprise/{enterprise_id}/device/{device_id}/",
      "enterprise": "https://{example}-api.esper.cloud/api/enterprise/{enterprise_id}/"
    }
  ]
}