WarrantyWizard & RMM Integration

Modified on Mon, Oct 20 at 6:52 PM

WarrantyWizard · RMM Integration

Overview

Connect your RMM (Kaseya, Datto, ConnectWise, NinjaOne, or N-Able) to synchronize device details (make, model, serial, warranty dates) into WarrantyWizard for automated warranty insights and reporting.

Note
You’ll need API credentials from your RMM (Base URL, Key, and Secret / Client ID & Secret). Create an API user in your RMM first if you don’t have one.
Section 1

Access the RMM Integration Page

Navigate to the central place where you’ll connect your RMM to WarrantyWizard.

  1. Log in to the Invarosoft Partner Portal with your admin credentials.
  2. Go to Settings → WarrantyWizard → RMM Integration.
  3. Select your RMM: Kaseya, Datto, ConnectWise, NinjaOne, or N-Able.
Tip: If you don’t see your RMM listed, verify your portal role has admin permissions.
Section 2

Enter Credentials & Start Your First Sync

These steps are the same regardless of the RMM you choose. Platform-specific roles/scopes are configured inside your RMM.

  1. Collect your RMM API details. Typically: Base API URL, API Key, and API Secret (or Client ID/Secret).
  2. Paste credentials into the Integration form. Double-check for extra spaces; store secrets in a secure vault.
  3. Click Test Connection. You should see success if the API user and scopes/roles are correct.
  4. Save & Start Sync. Initial ingestion can take a few minutes depending on device count.
Troubleshooting
  • Invalid credentials: Regenerate the API key/secret and confirm the Base URL (region-specific for some RMMs).
  • Permission/scope errors: Ensure your API user has read access to devices/agents/audit endpoints.
  • Network timeouts: Allow outbound traffic to your RMM API and whitelist WarrantyWizard egress as required.

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