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
Ticketing → Get Statuses
AI-generatedSummary
Retrieve all available ticket statuses from NinjaOne's ticketing system.
Inputs
- Authentication — Choose the authentication method for the API call; options are OAuth2 (Authorization Code) or Client Credentials. Defaults to OAuth2.
Output shape
a list of ticket status objects representing available statuses in the ticketing system
The returned data contains the full collection of ticket statuses usable for tickets. No input parameters besides authentication are needed.
Examples
Example 1: Retrieve all ticket statuses
Set Resource to 'Ticketing' and Operation to 'Get Statuses'. Choose the authentication method, then execute the node to receive a list of ticket statuses.