nexalwarenexalwaredocs
API ReferenceEvents

List a single device's audit log

Dashboard-only

This mirrors what a human does from the Nexalware web app - it's not meant to be automated by a third-party integration, even though a session token from Log in can technically call it. If you're building an integration that controls devices, use an API key instead: have an Owner/Admin grant it access to a device (a DeviceGrant), and use the Device Control endpoints.
GET
/api/v1/devices/{deviceId}/events

Same event log as GET /events, scoped to one device. Use before (an event id from a previous response) to page further back.

Authorization

sessionAuth
AuthorizationBearer <token>

A session token for an existing account, obtained from POST /auth/login (see the Authentication endpoints) - not an API key. Endpoints marked with this scheme reject API key callers outright, regardless of what that key is granted. Outside the Authentication endpoints themselves, everything requiring this scheme manages dashboard resources (rules, grants, keys, device configuration, command catalogs) and mirrors what a human does in the Nexalware web app - it is not meant to be automated by a third-party integration the way the Device Control and Schedules endpoints are.

In: header

Path Parameters

deviceId*string

Query Parameters

limit?|
Rangevalue <= 200
before?string

Response Body

application/json

application/json

curl -X GET "https://example.com/api/v1/devices/dev_a1b2c3/events"
[  {    "id": "string",    "deviceId": "string",    "deviceName": "string",    "eventType": "string",    "description": "string",    "timestamp": 0,    "source": "string"  }]

Update a device's custom command PATCH

Previous Page

List recent events across your whole account GET

A paginated audit log across every device you own - device online/offline, commands sent, unauthorized attempts, schedule changes. Use `cursor` from a previous response to page further back.