nexalwarenexalwaredocs
API ReferenceEvents

List recent events across your whole account

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/events

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.

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

Query Parameters

limit?|
Rangevalue <= 200
cursor?string

Response Body

application/json

application/json

curl -X GET "https://example.com/api/v1/events"
{  "data": [    {      "id": "evt_x1y2z3",      "deviceId": "dev_a1b2c3",      "deviceName": "Garage Light",      "eventType": "COMMAND_SENT",      "description": "Command \"ON\" sent via API key",      "timestamp": 1732000000000,      "source": "apikey"    }  ],  "total": 1,  "hasMore": false,  "cursor": null}

List a single device's audit log GET

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

Grant an API key or team member access to a device POST

This is how an API key gets permission to call device commands it has none by default. Provide exactly one of `apiKeyId` or `membershipId`. Add `subDeviceId` to narrow the grant to one sub-device behind this device (an orchestrator "master") instead of the whole device - omit it to reach every sub-device behind the device, same as today. Requires an Owner or Admin session; API keys cannot create grants for themselves or anyone else.