Actions120
- Alert Actions
- Backup Actions
- Custom Field Actions
- Device Actions
- Document Template Actions
- Group Actions
- Knowledge Base Article Actions
- Location Actions
- Organization Actions
- Organization Document Actions
- Query Actions
- Alerts
- Antivirus Status
- Antivirus Threats
- Backup Usage
- Computer Systems
- Custom Fields
- Custom Fields (Detailed)
- Device Health
- Disks
- Logged-On Users
- Network Interfaces
- Operating Systems
- OS Patch Installs
- OS Patches
- Policy Overrides
- Processors
- RAID Controllers
- RAID Drives
- Scoped Custom Fields
- Scoped Custom Fields (Detailed)
- Software
- Software Patch Installs
- Software Patches
- Volumes
- Windows Services
- Related Item Actions
- Software License Actions
- System Actions
- Get Activities
- Get Contacts
- Get Device Custom Fields
- Get Device Roles
- Get Devices (Detailed)
- Get End Users
- Get Jobs
- Get Locations
- Get Notification Channels
- Get Notification Channels (Enabled)
- Get Organizations (Detailed)
- Get Policies
- Get Scheduled Tasks
- Get Scripting Languages
- Get Scripts
- Get Software Products
- Get Technicians
- Get User Roles
- Ticketing Actions
- User Actions
- Webhook Actions
Query → Logged-On Users
AI-generatedSummary
Query NinjaOne for logged-on user records across devices. Optionally filter by pagination cursor and page size, plus device approval status, class, IDs, location, online status, organization, or role.
Inputs
- Authentication (required) — Choose OAuth2 (Authorization Code) or Client Credentials and configure the matching NinjaOne credentials.
- Filters — Optional query filters: Cursor and Page Size control pagination; Approval Status, Device Classes, Device ID, Location ID, Online Status, Organization ID, and Role ID restrict which devices are included. ID fields accept comma-separated values.
Output shape
A list of items, each containing one logged-on user record returned by NinjaOne.
The operation makes one GET request to the logged-on-users query endpoint. It passes the supplied cursor, page size, and device filters as query parameters; it does not automatically fetch subsequent pages. If the API returns a single object instead of an array, that object is emitted as one item.