N-Able RMM Integration

Modified on Wed, May 27 at 10:52 AM

API Integration

N-able N-central Integration

Connect N-able N-central to synchronize device inventory, including make, model, serial number, and warranty dates, into WarrantyWizard for automated reporting and proactive warranty tracking.

Overview

To programmatically access N-able N-central APIs, we recommend creating a dedicated API-only user. This user can access the public APIs but cannot access the N-central user interface.

Important: If you attempt to log in to the N-central interface as an API-only user, you will receive the message: “This user account does not have access to the UI.”
Prerequisites
Administrator AccessAdministrator access to N-able N-central
API-only UserA dedicated API-only user configured for public API access
Role & Access GroupThe API-only user must have the appropriate Role and Access Group assigned
JSON Web TokenA generated JSON Web Token for API authentication
Registered DevicesDevices must already exist in N-able N-central for synchronization
Tip: Use a dedicated API-only user for integrations to improve security, simplify auditing, and avoid using a standard user account for API calls.
Step 1

Create the API-only User in N-able N-central

  1. Go to Administration → User Management → Users.
  2. Click Create User.
  3. Enter the new user information and password.
  4. Assign the required roles and access groups. A user can have more than one role or access group:
    • Click the Role tab, then click Assign Roles. Select one or more roles and click Assign.
    • Click the Access Groups tab, then click Assign Access Groups. Select one or more access groups and click Assign.
  5. Disable two-factor authentication:
    • Click the User Details tab.
    • Click the User Information tab.
    • Under Access, clear the checkbox next to Use Two-Factor Authentication.
  6. Click Save.
Note: Two-factor authentication must be disabled for this API-only user so the JSON Web Token can be passed for API authentication.
Step 2

Configure API Access for the User

  1. From the Users list, select the login name of the user you just created.
  2. The Modify User dialog opens.
  3. Click the API Access tab.
  4. Select the API-Only User checkbox.
  5. Click Generate JSON Web Token.
  6. Copy the token and store it securely. You will need this token for API authentication.
  7. Click OK, then click Save.
Confirmation: The new user appears in the Users list. You can identify API users in the API-Only User column. If a Role and Access Group were assigned, a triangle appears next to the user name.
Step 3

Generate a JSON Web Token

A JSON Web Token enables communication with N-able N-central APIs. Depending on the integration requirements, authentication may use a traditional username and password combination, a username and JSON Web Token combination, or only the JSON Web Token.

JSON Web Tokens are generated for a specific user. They can be generated while creating a new user or by modifying an existing user.

  1. Click Administration → User Management → Users.
  2. Click Create User, or select the name of an existing user.
  3. Click the API Access tab.
  4. Click Generate JSON Web Token.
  5. Copy the token for login or API use.
  6. Click Save to exit.
Security Note: Store the JSON Web Token securely. Treat it like a password and do not share it in plain text, public tickets, or unsecured documentation.
Step 4

Connect N-able N-central to WarrantyWizard

  1. In the Invarosoft portal, go to Integrations .
  2. Select N-able N-central as the vendor.
  3. Enter the required authentication details, including the API Base URL, API-only User login, and JSON Web Token.
  4. Click Test Connection to validate access.
  5. Click Save & Start Sync.
  6. Allow a few minutes for the initial sync, depending on the number of devices in N-able N-central.
Video Guide

N-able N-central API Access Walkthrough

Use the video below as an additional visual reference when creating the API-only user and generating the JSON Web Token.

Troubleshooting
  • Cannot log in to the N-central UI: This is expected for API-only users. API-only users do not have access to the user interface.
  • 401/403 authorization errors: Confirm the API-only user has the correct Role, Access Group, and permissions for the API endpoint being used.
  • Token authentication fails: Confirm that two-factor authentication has been disabled for the API-only user and that the JSON Web Token was copied correctly.
  • Invalid URL: Confirm the API Base URL matches your N-able N-central environment.
  • No data synced: Verify that devices exist in N-able N-central and are visible to the API-only user through the assigned Access Group.
  • Limited or missing device data: Review the assigned roles and permissions to ensure the API-only user can access the required device and asset information.
Source: Internal RMM Integration Setup notes and N-able N-central API-only user configuration guidance.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article