How to get your N-able N-sight API key
Create or reuse the N-sight key in General Settings, save the territory address supplied with it, and confirm that its assigned permissions can see the clients you want to protect.
Generate an N-able N-sight API key, select the correct territory server, understand Agent Key visibility, and fix connection errors.
On this page
Prerequisites
Sign in as a Superuser, non-Classic Administrator, a login with the required General permissions, or an enabled Agent Key. N-able recommends reusing an existing API key when one already exists because regenerating it stops integrations using the previous key.
Generate the API key
- In All Devices, open Settings > General Settings > API.
- Select Generate, or Regenerate only when intentionally replacing the current key.
- Record the key. You can optionally have N-sight email the key and server URL to an approved recipient.
- Select OK to apply the change.
Store the key as a secret. N-sight puts it in the API query string, so never include a real request URL in tickets or logs.
Find the territory server URL
Use the server URL supplied with the key or choose the exact account territory from N-able's current territory list. The region is determined by where the account is registered, not the operator's location. RMMBackup accepts only documented HTTPS territory origins and constructs the /api/ query path itself.
Permissions and client visibility
N-sight's API key is linked to Agent Key General permissions and client-group scope rather than a separate OAuth scope list. The selected account must be allowed to read the clients and enabled features used by the chosen collections: clients/sites, devices, inventory, checks, alerts, outage and capacity history, patches, antivirus, templates, settings, licensing, Backup & Recovery status, and Active Directory users.
Feature-specific collections can be unavailable when the feature is disabled or not visible. Do not widen the Agent Key to all clients unless the backup is intended to cover all clients. See N-sight export and coverage notes.
Troubleshoot connection problems
- Authentication failure: verify the key was not regenerated and that the selected territory matches the key.
- Only some clients appear: inspect the Agent Key's assigned client group and General permissions.
- A feature collection fails: confirm the feature is enabled and visible to the key; other collections may still succeed.
- Empty response: test client-group scope and the selected service. Empty visible scope is different from invalid credentials.
- Throttling: N-able documents a maximum of 60 automated calls per minute.
Frequently asked questions
Are N-sight and N-central API credentials interchangeable?
No. They are separate products with different APIs; this guide and RMMBackup connection apply only to N-able N-sight.
Why does the API show only some clients?
An Agent Key assigned to a client group can return only clients in that group. A partial or empty response is not automatically an invalid API key.
Official source
Related N-able N-sight integration
Review current N-able N-sight backup coverage and availability.