NinjaOne ticketing API is one of 22 APIs that NinjaOne publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include ticketing. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.
This API exposes 13 operations across 12 paths, and defines 36 schemas. It is described by OpenAPI 3.0.1, at version 2.0.9-draft.
Requests are made against the base URL https://app.ninjarmm.com/v2.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
NinjaOne ticketing API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (bearer) (oauth2).
An API key is passed in the cookie as sessionKey (sessionKey).
By default, every request must be authenticated.
Paths & Operations 13
Across 12 paths, the API surfaces 13 operations — 9 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
ticketing
Schemas 36
The contract defines 36 schemas that model the data the API accepts and returns. The most detailed are TicketDTO (20 properties), TicketLogEntryPublicApiDTO (20 properties), UpdateTicket (17 properties), NewTicket (17 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from NinjaOne 12
Other APIs NinjaOne publishes across the network.