NinjaOne icon

NinjaOne

Ninja One Public API documentation. <br><br>See also: <br> <a href="https://resources.ninjarmm.com/API/Ninja+RMM+Public+API+v2.0.5+Device+Filter+Syntax.pdf">Device Filter syntax</a><br><a href="https://app.ninjarmm.com/apidocs-beta/core-resources/articles/webhooks/overview">Webhooks</a>

Actions309

Ticketing → Update ticket

AI-generated

Summary

Update an existing ticket in the NinjaOne Ticketing system by providing the ticket ID, version, client ID, ticket form ID, subject, status, requester UID, and optional additional fields to modify various ticket attributes.

Inputs

  • ticketId (required) — The unique identifier of the ticket to update.
  • version (required) — The current version number of the ticket to ensure concurrency control.
  • clientId (required) — The identifier of the client (organization) associated with the ticket.
  • ticketFormId (required) — Identifier of the ticket form to which the ticket belongs.
  • subject (required) — The subject or title of the ticket.
  • status (required) — The current status of the ticket (e.g., '1000').
  • requesterUid (required) — Unique identifier of the user who requested the ticket.
  • additionalFields — Optional fields to specify extra ticket details such as locationId, nodeId, type, cc, assignedAppUserId, severity, priority, parentTicketId, tags, attributes, additional assigned technician IDs, and follow-up time.
  • options — Additional request options such as custom JSON body overrides, custom HTTP headers, query parameters, batching settings, debug output toggle, pagination settings, and request timeout.

Output shape

a single updated ticket record as returned by the NinjaOne API

The response includes the updated ticket object reflecting the changes made. Debug information can be optionally included if enabled. Pagination and batching options configure request behavior but do not affect a single update operation response.

Links

Discussion