New API Features - February 5, 2026

New Endpoints

The following resources have been added to the API.

Get Event by ID

You can now retrieve a specific event using its unique identifier.

curl --request GET \
     --url https://api.cxxx.eagleeyenetworks.com/api/v3.0/events/aLP130ZuaWAnv3qcKhFi \
     --header 'accept: application/json'

using RestSharp;


var options = new RestClientOptions("https://api.cxxx.eagleeyenetworks.com/api/v3.0/events/aLP130ZuaWAnv3qcKhFi");
var client = new RestClient(options);
var request = new RestRequest("");
request.AddHeader("accept", "application/json");
var response = await client.GetAsync(request);

Console.WriteLine("{0}", response.Content);

import requests

url = "https://api.cxxx.eagleeyenetworks.com/api/v3.0/events/aLP130ZuaWAnv3qcKhFi"

headers = {"accept": "application/json"}

response = requests.get(url, headers=headers)

print(response.text)

const url = 'https://api.cxxx.eagleeyenetworks.com/api/v3.0/events/aLP130ZuaWAnv3qcKhFi';
const options = {method: 'GET', headers: {accept: 'application/json'}};

fetch(url, options)
  .then(res => res.json())
  .then(json => console.log(json))
  .catch(err => console.error(err));

Updated Endpoints

The following endpoints have been updated with new features.

List Events with Data Filtering

The List Events endpoint now supports data filtering, allowing you to refine your event queries based on fields within specific event data schemas. These filters follow the naming pattern data.{schemaName}.{fieldName} and apply to all event types. Events that do not contain the specified schema will be excluded from results.

For example, when searching for both motion and device status events with a connectionStatus filter, motion events will not be returned (since they don't have connectionStatus), and only device status events that match the connectionStatus criteria will be returned.

Data filtering can be used on either the List Events or List Recent Events by Type endpoints.

/events:listRecentByType

curl --request GET \
     --url 'https://api.cxxx.eagleeyenetworks.com/api/v3.0/events:listRecentByType?data.een.humanValidationDetails.v1.isValid__ne=true' \
     --header 'accept: application/json'

using RestSharp;


var options = new RestClientOptions("https://api.cxxx.eagleeyenetworks.com/api/v3.0/events:listRecentByType?data.een.humanValidationDetails.v1.isValid__ne=true");
var client = new RestClient(options);
var request = new RestRequest("");
request.AddHeader("accept", "application/json");
var response = await client.GetAsync(request);

Console.WriteLine("{0}", response.Content);

import requests

url = "https://api.cxxx.eagleeyenetworks.com/api/v3.0/events:listRecentByType?data.een.humanValidationDetails.v1.isValid__ne=true"

headers = {"accept": "application/json"}

response = requests.get(url, headers=headers)

print(response.text)

const url = 'https://api.cxxx.eagleeyenetworks.com/api/v3.0/events:listRecentByType?data.een.humanValidationDetails.v1.isValid__ne=true';
const options = {method: 'GET', headers: {accept: 'application/json'}};

fetch(url, options)
  .then(res => res.json())
  .then(json => console.log(json))
  .catch(err => console.error(err));

New Events

The following new event types have been added.

Device Cloud Connection Status Update Event

Generated when a device's connection status to the cloud changes. The event represents the span of time the device stays in the given state, and a null endTimestamp indicates it was still in the given state when the event was retrieved.

View Event Documentation

Edge Reported Device Status Event

Generated when a device's status changes. The event represents the span of time the device stays in the given state, and a null endTimestamp indicates it was still in the given state when the event was retrieved.

View Event Documentation

Object Line Cross Count Event

Generated when counting analytics is enabled and an object crosses a predefined virtual line or boundary within a monitored area. This event is distinct from object line cross events and is used specifically for statistical counting purposes rather than alerting.

View Event Documentation