Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

NinjaOne organization API

Organizations

NinjaOne organization API is one of 22 APIs that NinjaOne publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include organization. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 8 operations across 7 paths, and defines 15 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.

8 operations 7 paths 15 schemas 7 GET1 PATCH

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 2

NinjaOne organization 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 8

Across 7 paths, the API surfaces 8 operations — 7 GET, 1 PATCH. Each is listed below with its method, path, parameters, and response codes.

organization 8

Organizations

GET
/v2/organization/{id}/locations
Organization locations
getOrganizationLocations 1 param → default
GET
/v2/organization/{id}/end-users
List users
getEndUsers 2 params → default
GET
/v2/organization/{id}/locations/{locationId}/backup/usage
Organization location backup usage
getLocationUsage 2 params → 200
GET
/v2/organization/{id}/custom-fields
Organization custom fields
getNodeCustomFields_1 1 param → default
PATCH
/v2/organization/{id}/custom-fields
Update Field Values
updateNodeAttributeValues_1 1 param body → default
GET
/v2/organization/{id}
Organization information
getOrganization 1 param → default
GET
/v2/organization/{id}/devices
Organization devices
getOrganizationDevices 3 params → default
GET
/v2/organization/{id}/locations/backup/usage
Organization locations backup usage
getOrganizationLocationUsage 1 param → 200

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are NodeWithDetailedReferences (24 properties), User (20 properties), LocationBackupUsageSummary (19 properties), BackupUsage (14 properties). Each schema is shown below with its type and property counts.

User
object
Assigned device owner
20 properties
LocationBackupUsageSummary
object
19 properties
Policy
object
Assigned policy (overrides organization and location policy mapping)
9 properties
NodeReferences
object
Expanded entity references
8 properties
Location
object
Location
7 properties
Organization
object
Organization
7 properties
BackupUsage
object
Device Backup Usage
14 properties
OrganizationDetailed
object
10 properties
OrganizationSettings
object
Organization settings
5 properties
WarrantyDates
object
Warranty Info
3 properties
NodeRolePolicyAssignment
object
Node role policy assignments
2 properties
Maintenance
object
Maintenance mode status
3 properties
NodeRole
object
Device Role
11 properties
FeatureSettings
object
Feature/product/integration configuration settings
4 properties
NodeWithDetailedReferences
object
Device information.
24 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ninjaone-organization-api-openapi.yml Raw ↑

Other APIs NinjaOne publishes across the network.

NinjaOne Asset Tags API
NinjaOne Backup API
NinjaOne Checklist Templates API
NinjaOne Custom Fields API
NinjaOne Custom Tabs API
NinjaOne devices API
NinjaOne Document Templates API
NinjaOne groups API
NinjaOne Knowledge Base Articles API
NinjaOne Location API
NinjaOne management API
NinjaOne Organization Checklists API