Level API

The common uses are adding a device’s health to a ticket, running one of your Level automations on the ticket’s device and reading its output, and tagging or moving devices so your automations pick them up.

Automatically enabled when you configure Level permissions in your agent workflow.

What It Does

Find a device by hostname, serial number or last signed-in user, and read its hardware, operating system, disks, memory, network interfaces, motherboard and security detail
Read a device’s alerts, and resolve one
Read pending, installed and failed operating system updates per device
Run an automation on chosen devices through its webhook trigger, and read each run’s status and step output
Tag and untag devices; create, rename and delete tags
Rename a device, change its notes, move it to another group, or delete it
Read and change groups, and set custom field values on the organization, a group or a device
Read the Level activity log

Permission Groups

Group	Covers
Devices	Devices and their detail; renaming, notes, moving and deleting a device
Groups	The group tree; creating, renaming, moving and deleting a group; putting devices in a group or taking them out
Alerts	Monitor alerts per device, and resolving one
Updates	Operating system updates per device (read only)
Automations	Automations, their webhook triggers, running one, and each run’s step output
Tags	Tags; tagging and untagging devices; creating, renaming and deleting a tag
Custom Fields	Custom fields and their values; setting and clearing a value; creating, renaming and deleting a field
Activity Log	Level’s activity log (read only)

Access Profiles

Profile	What runs on its own	What asks a technician
Read Only	Every read	No write is allowed
Helpdesk	Every read, and resolving an alert	Device changes, tags and automation runs; group and custom field changes are not allowed
IT Admin	Every read, device changes, tags, alerts and automation runs	Group and custom field changes, and the changes that always ask
Full Automation	Every read and write	The changes that always ask

Safety Controls

Control	Behavior
The ticket’s customer only	On a run for a ticket that names a company, every call carries the Level group the ticket’s company is mapped to, and Neo sends it only when each device, group, alert, update and automation run it names sits in that group or under it. A device list must be narrowed to the group. A group that holds another customer’s mapped group gets no customer-scoped call Creating, renaming or deleting a tag or custom field, and taking devices out of a group, are refused on a ticket run
Always asks a technician	Deleting a device or a group
Automations name their devices	An automation run must name at least one device; Neo never runs one on every device its trigger admits
Webhook tokens	Neo hides each webhook trigger’s token in every answer and error, and sends a run to the token itself
Custom field values	Neo hides every custom field value in every answer, and the details of custom field changes in the activity log, because any one can hold a password or key; agents can still set values, and a technician reads them in Level

Getting started

Core

Triggered & Scheduled Agents

Chat Agents

Integrations

Product

Workflows

Customizing Neo

What It Does

Permission Groups

Access Profiles

Safety Controls

​What It Does

​Permission Groups

​Access Profiles

​Safety Controls

What It Does

Permission Groups

Access Profiles

Safety Controls