NinjaOne · OAuth Scopes
NinjaOne OAuth Scopes
OAuth 2.0
searched
NinjaOne publishes 4 OAuth 2.0 scopes via the clientCredentials and authorizationCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the NinjaOne API on a user’s behalf.
Tokens are issued from https://app.ninjarmm.com/ws/oauth/token.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
CompanyDeveloper ToolsIT ManagementRMMEndpoint ManagementMSPIT OperationsMonitoringAutomationTicketing
Scopes: 4
Flows: clientCredentials, authorizationCode
Method: searched
OAuth endpoints
Authorization URL
https://app.ninjarmm.com/ws/oauth/authorize
https://app.ninjarmm.com/ws/oauth/authorize
Token URL
https://app.ninjarmm.com/ws/oauth/token
https://app.ninjarmm.com/ws/oauth/token
Flows
clientCredentialsauthorizationCode
clientCredentialsauthorizationCode
Scopes (4)
| Scope | Description | Flows |
|---|---|---|
| monitoring | Read-only access to monitoring data and organization structure — devices, alerts, activities, and reports. Grants GET access across the platform. | clientCredentials, authorizationCode |
| management | Modify device and organization information — create organizations, add devices, run scripts, manage policies, tickets, and custom fields. | clientCredentials, authorizationCode |
| control | Enable remote access / remote control of endpoints via the API. | clientCredentials, authorizationCode |
| offline_access | Request a refresh token (authorization-code flow) so an access token can be renewed without re-authenticating. | authorizationCode |
📄 Provider scope reference: https://www.ninjaone.com/docs/application-programming-interface-api/oauth-token-configuration/