Skip to main content

​
Overview

The Ninja RMM integration enables ThreatAware to collect read-only data from your Ninja RMM platform, providing visibility into remote management activities and device status.
Connection Method: API Setup Time: 10 minutes Access Required: Ninja RMM Administrator account

​
Data collected

The Ninja RMM integration provides:
  • Device inventory and status
  • Remote management activity logs
  • System information and health metrics
  • Device asset details

​
Use cases

Device Monitoring

Track device status and health across your managed environment

Remote Management Tracking

Monitor remote support activities and management operations

Inventory Management

Maintain device inventory with real-time status updates

Compliance Verification

Verify remote management controls are properly configured

​
Setup instructions

1

Log in to ThreatAware

Access the ThreatAware dashboard and navigate to Settings → Integrations.
2

Locate Ninja RMM

Use the search bar to find Ninja RMM in the integrations list.
3

Click Connect

Click Connect and a pop-up window will appear.
4

Generate API Credentials

Log in to your Ninja RMM platform with an administrator account.
  • Navigate to Settings > Apps > Legacy API
  • Click Generate New API Key
  • Copy the ID (this is your API key)
  • Copy the Secret (this is your API secret)
The API secret will only be displayed once. Copy it securely before closing the dialog.
5

Determine Your API Subdomain

Identify your API subdomain based on your Ninja RMM region:
  • EU Tenant: Use eu-api
  • Other Regions: Use api
Check your Ninja RMM account settings or contact support if unsure about your region.
6

Configure in ThreatAware

In the ThreatAware pop-up window, enter:
  • API ID: The ID copied from Ninja RMM
  • API Secret: The Secret copied from Ninja RMM
  • API Subdomain: api or eu-api based on your region
  • Click Connect to establish the integration
7

Verify Connection

After connecting, verify the integration status:
  • Check that the Integration Status shows as Active
  • Wait for initial data synchronization
  • Verify device data appears in ThreatAware

​
Required credentials

Field Name: Ninja RMM API ID Type: String Description: The ID generated from Ninja RMM Legacy API settingsExample: abc123def456
Field Name: Ninja RMM API Secret Type: Password (encrypted) Description: The secret generated from Ninja RMM Legacy API settings
Store this credential securely. It will only be displayed once during generation.
Field Name: API Subdomain Type: String Description: Your API region subdomainValid Values:
  • api (default for most regions)
  • eu-api (for EU tenants)

​
Verification and testing

After setup, verify the integration is working correctly:
  1. Check Integration Status
    • Navigate to Settings → Integrations in ThreatAware
    • Confirm the Ninja RMM integration shows Active status
  2. Verify Data Collection
    • Wait for initial data sync
    • Search for a known device in ThreatAware
    • Verify Ninja RMM data appears in device details
  3. Test Queries
    • Create a test query to filter devices with Ninja RMM data
    • Verify the device list matches your Ninja RMM inventory

​
Troubleshooting

Symptoms: Integration status shows authentication failureSolutions:
  • Verify the API ID and API Secret are correct
  • Ensure the API key hasn’t expired in Ninja RMM
  • Check that you copied the entire ID and Secret without extra spaces
  • Regenerate API credentials if needed
Symptoms: Connection fails or times outSolutions:
  • Verify the correct API subdomain for your region
  • Check if you are on an EU tenant (use eu-api)
  • Contact Ninja RMM support to confirm your region
  • Try the alternate subdomain if unsure
Symptoms: Integration shows active but no device data appearsSolutions:
  • Wait up to 10 minutes for initial data sync
  • Verify there are managed devices in your Ninja RMM account
  • Check API user permissions in Ninja RMM
  • Review integration logs in ThreatAware (contact support if needed)
Symptoms: Integration connects but shows permission errorsSolutions:
  • Ensure the user account used to generate API credentials is an administrator
  • Regenerate API credentials with proper admin permissions
  • Contact Ninja RMM support to verify account permissions

​
Additional resources

Ninja RMM Documentation

Official Ninja RMM documentation

ThreatAware Support

Contact ThreatAware support for integration assistance

​
Best practices

Security Considerations
  • Store API credentials securely in your password manager
  • Regenerate API keys periodically per your security policy
  • Monitor authentication failures in the integration logs
  • Only grant administrator permissions to the API account if necessary
Integration Management
  • Test the connection immediately after setup
  • Verify device data is syncing as expected
  • Check the integration status regularly
  • Document your API subdomain for future reference