How to get your NinjaOne API client ID and client secret
Create a dedicated NinjaOne application for RMMBackup, give it read-only monitoring access, and save the client ID, client secret, and account region. The steps below explain each setting and how to validate the connection.
Create dedicated NinjaOne credentials, grant read-only monitoring access, choose the account region, and troubleshoot connection errors.
On this page
Prerequisites
NinjaOne says only system administrators can configure Public API OAuth applications. Create a separate application for the backup connection so its credentials and scope can be reviewed or revoked independently.
Register the API application
- Open Configuration > Apps > API > Client App IDs. Some current NinjaOne screens label the first menu Administration rather than Configuration.
- Select Add and choose API Services (machine-to-machine).
- Name the application.
- Select only the Monitoring scope.
- Enable Client Credentials as the allowed grant type and save.
- Copy the resulting client ID and client secret into an approved secret store.
Do not select Management or Control: those allow modification or remote access and are unnecessary for the read-only collector.
Find the regional API URL
Use the regional NinjaOne instance where the tenant signs in. Official instance families include app, us2, eu, oc, ca, jp, and fed under ninjarmm.com. RMMBackup uses a fixed region selector rather than accepting arbitrary hosts.
The client credentials flow posts to the tenant's /ws/oauth/token path and requests monitoring. Access tokens are short-lived; the application client ID and secret are the durable credentials.
Minimum permission scope
The Monitoring scope is documented as read-only access to monitoring data and organization structure. RMMBackup collections include organizations, locations, devices, inventory, services, patches, alerts, activities, jobs, policy context, groups, script metadata, custom fields, knowledge base content, and organization documentation.
NinjaOne's specifications do not assign a separate fine-grained OAuth scope to every operation. Validate every selected collection in the real tenant before enabling backups, because licensing and tenant visibility may still restrict responses.
Troubleshoot OAuth and visibility
- Invalid client: verify both values came from the same API Services app and the correct regional instance.
- Invalid grant: confirm Client Credentials is enabled for an API Services application.
- Insufficient scope: request
monitoringand confirm it is selected on the app; do not solve this by adding write scopes. - Empty or partial inventory: check organization visibility, licensed modules, and filters. Empty data is not proof of invalid credentials.
- Wrong region: use the tenant's NinjaOne instance, not a guessed global endpoint.
Connect RMMBackup
In Settings > Integrations, choose NinjaOne Beta, select the region, and enter the client ID and secret. Save and validate before enabling backups. Continue with the NinjaOne integration page, backup guide, and data export guide.
Frequently asked questions
Which NinjaOne OAuth scope is appropriate for backup reads?
Monitoring is the documented read-only scope for monitoring data and organization structure. Do not add Management or Control for this read-only integration.
Is the NinjaOne integration available in RMMBackup now?
Yes. NinjaOne is available in Beta with connection validation, source selection, manual and scheduled backups, snapshots, comparisons, and ZIP exports.
Official source
Related NinjaOne (formerly NinjaRMM) integration
Review current NinjaOne (formerly NinjaRMM) backup coverage and availability.