How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
NinjaOne

NinjaOne ticketing API

ticketing

Documentation Provider Profile APIs.io OpenAPI GitHub

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.2.0, at version 2.0.9-draft.

Requests are made against a single base URL, https://app.ninjarmm.com/v2.

13 operations 12 paths 36 schemas 9 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.9-draft
Base URL
https://app.ninjarmm.com/v2
Authentication
HTTP Bearer, API Key
Contact
api@ninjarmm.com
Resource Areas
1

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 13

ticketing

POST
/v2/ticketing/ticket
Create ticket
create body → default
POST
/v2/ticketing/ticket/{ticketId}/comment
Add comment to ticket
createComment 1 param body → default
GET
/v2/ticketing/ticket/{ticketId}
Ticket
getTicketById 1 param → default
PUT
/v2/ticketing/ticket/{ticketId}
Update ticket
update 1 param body → default
GET
/v2/ticketing/ticket/{ticketId}/log-entry
List ticket log entries
getTicketLogEntriesByTicketId 5 params → default
GET
/v2/ticketing/attributes
List ticket attributes
getTicketAttributes → default
GET
/v2/ticketing/contact/contacts
List contacts
getContacts_1 → default
GET
/v2/ticketing/ticket-form/{id}
Ticket form
getTicketFormById 1 param → default
GET
/v2/ticketing/ticket-form
List ticket forms
getTicketForms → default
GET
/v2/ticketing/statuses
Get list of ticket status
getAllStatuses → default
GET
/v2/ticketing/trigger/boards
List boards
getBoards → default
POST
/v2/ticketing/trigger/board/{boardId}/run
List of tickets for board
getTicketsByBoard 1 param body → default
GET
/v2/ticketing/app-user-contact
List of users by user type
getAllUserAndContacts 5 params → 200

Schemas 36

The contract defines 36 schemas that model the data the API accepts and returns. The most detailed are TicketLogEntryPublicApiDTO (20 properties), TicketDTO (20 properties), NewTicket (17 properties), UpdateTicket (17 properties). Each schema is shown below with its type and property counts.

TicketBoardScrollingRequestDTO
object
6 properties
TicketStatusPublicApiDTO
object
4 properties
Condition
object
2 properties
AttributeContent
object
7 properties
TicketDashboardPublicApiDTO
object
2 properties
TicketFormContent
object
2 properties
AttributeContentAdvancedSettings
object
10 properties
AppUserAndContactPublicApiDTO
object
8 properties
Rule
object
3 properties
TicketingBoardPublicApiDTO
object
11 properties
TicketLogEntryAutomationDTO
object
4 properties
UpdateTicket
object
17 properties 6 required
ContactResponseDTO
object
12 properties
NewTicket
object
17 properties 4 required
TicketingAttributePublicApiDTO
object
14 properties
AgreementDTO
object
2 properties
TicketLogEntryPublicApiDTO
object
20 properties
TechniciansTaggedMetadataDTO
object
5 properties
AttributeContentAdvancedSettingsDateFilters
object
2 properties
AttributeContentValue
object
4 properties
CarbonCopy
objectnull
2 properties
TicketingAttributeValue
objectnull
3 properties 2 required
CcList
object
2 properties
TicketMetadata
object
7 properties
SortBy
object
2 properties
AgreementProductTimeEntryDTO
object
2 properties
EndUserCustomization
object
3 properties
TicketFormPublicApiDTO
object
10 properties
AttributeContentAdvancedSettingsNumericRange
object
2 properties
NewTicketLogEntry
object
5 properties 1 required
TicketDTO
object
20 properties
TicketTimeEntryDTO
object
11 properties
AttributeValueDTO
object
3 properties
AttributeData
object
2 properties
TimerSettings
object
2 properties
AttributeContentAdvancedSettingsComplexityRules
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ninjaone-ticketing-api-openapi.yml Raw ↑

Other APIs NinjaOne publishes across the network.

NinjaOne Asset Tags API
AE Profile APIs.io
NinjaOne Backup API
AE Profile APIs.io
NinjaOne Checklist Templates API
AE Profile APIs.io
NinjaOne Custom Fields API
AE Profile APIs.io
NinjaOne Custom Tabs API
AE Profile APIs.io
NinjaOne devices API
AE Profile APIs.io
NinjaOne Document Templates API
AE Profile APIs.io
NinjaOne groups API
AE Profile APIs.io
NinjaOne Knowledge Base Articles API
AE Profile APIs.io
NinjaOne Location API
AE Profile APIs.io
NinjaOne management API
AE Profile APIs.io
NinjaOne organization API
AE Profile APIs.io
#Ticketing
← Back to N APIs
API Details
ID
ninjaone:ninjaone-ticketing-api
Base URL
https://app.ninjarmm.com/v2
Docs
https://app.ninjarmm.com/apidocs/
Provider
NinjaOne
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=ninjaone-ticketing-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ninjaone-ticketing-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of NinjaOne ticketing API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.