List a device's access grants

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.

Includes grants scoped directly to this device and grants scoped to its whole project both apply.

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 (schedules, rules, grants, keys, device configuration) 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 endpoints are.

In: header

Path Parameters

deviceId*string

Response Body

`application/json`

curl -X GET "https://example.com/api/v1/devices/dev_a1b2c3/grants"

[  {    "grantId": "string",    "appliesVia": "device",    "commands": [      "string"    ],    "scope": "READ",    "expiresAt": "2019-08-24T14:15:22Z",    "activeDays": [      0    ],    "activeFromMinute": 0,    "activeToMinute": 0,    "rateLimitPerMinute": 0,    "createdAt": "2019-08-24T14:15:22Z",    "subject": {      "type": "apikey"    }  }]

List a device's access grants

Authorization

Path Parameters

Response Body

200application/json

404application/json

`application/json`

`application/json`