- Application management
- RESTful API
- User API
- Device API
- Get devices
- Get devices extended
- Get device count
- Get device
- Get device by MAC address
- Get device by hostname
- Update device
- Get device threat
- Update device threat
- Get zone devices
- Get agent installer link
- Delete Devices
- Get Device Lifecycle Management settings
- Update Device Lifecycle Management Settings
- Exempt devices from the Device Lifecycle Management process
- Include devices in the Device Lifecycle Management process
- Reset the inactive period for a list of devices that are included in the Device Lifecycle Management process
- Global list API
- Policy API
- Zone API
- Threat API
- Memory protection API
- Detections API
- Package deployment API
- Detection rule API
- Detection rule sets API
- Detection exceptions API
- Device commands API
- Focus view API
- InstaQuery API
- CylanceOPTICS policy API
- Lockdown configurations API
Authorization
In response to the authentication request, the client will receive a response that contains at least the access token. The access token will contain the scopes that will dictate what can or cannot be done. This token is signed by the server and the client will merely echo it on every request as it tries to access resources.
The access token represents the identity of the requester as well as some attributes like scopes. This token will have an expiration and should be sent on every request in the authorization request header. Failing to do so will result in an HTTP/1.1 401 unauthorized response. Should the token be provided and prove to be legitimate but the server finds the action the caller is trying to attempt is not allowed (found in the scopes granted), an HTTP/1.1 403 forbidden will be returned.