Introduction

Regentra is a combined PSA and compliance platform for MSPs. Its Level integration imports the devices you manage in Level into Regentra as assets, so they appear in Regentra’s asset inventory, on tickets, and in your client portal.

Setup is short and mostly happens in Regentra. In Level you create a read-only API key, and optionally a webhook so device changes reach Regentra within seconds instead of waiting for the next scheduled sync.

ℹ️ NOTE: This integration was built and is maintained by Regentra. For the Regentra side of the setup, see their documentation: Level.io RMM Integration.

⚙️ PREREQUISITES

Level administrator access. API keys and webhooks are both admin-only.
A Regentra account with access to Settings → Integrations.

Regentra Integration

Create an API Key in Level

Regentra uses a Level API key to read your device inventory.

In Level, navigate to Settings → API keys.
Click + Create API key.
Enter a Description such as “Regentra integration”.
Select Read-only. Regentra reads device data from Level and writes nothing back, so a read-only key is enough.
Click Create key, then use the three-dot menu on the new row and choose Copy key.

Create API key dialog in Level settings with Read-only selected

See API Keys Settings for full details on managing keys.

Connect Regentra to Level

In Regentra, go to Settings → Integrations → Level.io RMM.
Paste the key you copied into the API key field.
Click Test Connection to confirm Regentra can reach the Level API.
Save the configuration, then click Sync Now to run the first import.

After the first import, Regentra pulls your full device inventory on a schedule of its own. Regentra documents this as every six hours.

What Syncs

Each Level device becomes an asset in Regentra, with these fields populated from Level:

Level	Regentra asset
Hostname	Device name
Serial number	Serial number
Operating system	OS
Manufacturer	Manufacturer
Model	Model
Online state	Online/offline status

The sync is one way. Regentra reads from Level and never writes back, so nothing you edit in Regentra changes a device in Level.

ℹ️ NOTE: Level does not collect hardware warranty dates, so warranty fields in Regentra stay manual entries.

Send Real-Time Device Updates with a Webhook

The scheduled sync is enough for most teams. Add a webhook if you want new devices, device changes, and deletions to reach Regentra immediately.

In Regentra, open Settings → Integrations → Level.io RMM and copy the webhook endpoint URL.
In Level, navigate to Settings → Webhooks and click + Add webhook.
Paste the Regentra endpoint into the URL field.
If Regentra gave you a signing secret for this endpoint, paste it into Secret. Otherwise leave it empty. Level only adds the X-Level-Signature header when a secret is set, and the receiving endpoint has to be built to verify it.
Leave the Enabled toggle on.
Under Events to send, choose Select types to send and check Device created, Device updated, and Device deleted.
Click Add webhook.

Add new webhook panel in Level settings with Select types to send chosen

Regentra confirms receipt of the first event and shows the webhook as Active on its side.

See Webhook Settings for the payload format, the delivery log, and retry behavior.

Test the Integration

Confirm the Level.io RMM integration in Regentra shows Connected.
Spot-check Regentra’s asset list against your Level device listing.
If you set up the webhook, rename a device in Level, then open Settings → Webhooks → Requests in Level and look for a Device updated delivery with a 2xx status code.

If a delivery failed, click the row to read the error message and response body. Level retries a failed delivery up to three times on its own, and you can click Re-run request once you have fixed the cause. Common causes are a mistyped endpoint URL, or a secret set on one side but not the other.

If assets are missing but the connection tests fine, the API key is the first thing to check. A deleted or rotated key stops the sync immediately and Regentra’s integration card switches to Error.

Ongoing Management

Rotate the key: create a new API key in Level, paste it into Regentra, test the connection, then delete the old key. Deleting a key takes effect immediately, so do it in that order.
Pause real-time updates: disable the webhook in Level. The scheduled sync keeps running.
Stop the integration: remove the API key from Regentra, or delete the key in Level.
Deleted devices: removing a device from Level does not delete its Regentra asset. Regentra keeps the record for history and updates its status.

⚠️ WARNING: If you connect both Level and NinjaOne to the same Regentra organization, Regentra treats NinjaOne as the higher-priority device source and retires the Level copy of any device that appears in both. See Regentra’s NinjaOne RMM Integration documentation.

FAQ

Do I need to enable Regentra on Level’s Integrations page? No. Settings → Integrations in Level covers ConnectWise PSA, HaloPSA, Zest, Hudu, and DeskDay. Regentra connects through the Level API and, optionally, a webhook, so there is nothing to toggle there.
Read-only or read and write for the API key? Read-only. Regentra only reads devices from Level. If a connection test or sync ever fails with a permissions error, check with Regentra before widening the key.
Is the webhook required? No. The scheduled sync works without it. The webhook only adds near-instant updates for teams that need current asset data between syncs.
Do Level alerts open Regentra tickets? Regentra’s Level integration documents device and asset sync, not alerting. Level can send Alert active and Alert resolved events to any endpoint, so ask Regentra whether their endpoint accepts them before you add those event types to the webhook.
Why does a device appear twice in Regentra? Regentra deduplicates devices from Level against devices from Microsoft Entra or Intune by matching serial number and hostname. A device with no serial number can land as two records until you merge them. See Regentra’s Level.io RMM Integration documentation.
Can I limit which Level devices sync? The Level side has no filter. A read-only API key can read every device in your Level organization, so any scoping happens in Regentra.
Who can set this up? A Level administrator, for the API key and the webhook, and a Regentra user with access to Settings → Integrations.