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 → Delete
AI-generatedSummary
Delete a ticket in NinjaOne by its Ticket ID, using either OAuth2 or Client Credentials authentication.
Inputs
- Authentication — Select the authentication method to use: OAuth2 (Authorization Code) or Client Credentials.
- Ticket ID (required) — The numeric ID of the ticket to delete.
Output shape
a JSON object indicating success or failure of the deletion operation
The operation performs an HTTP DELETE request to the NinjaOne API endpoint for the specified ticket ID. The response is a JSON object; in success cases, it may contain success confirmation, in failure cases an error may be returned.