Configure Huntress Integration

This guide walks you through connecting Huntress to MSPortal.ai using the guided setup wizard. The Huntress integration is currently in Beta.

Overview

Huntress provides Managed EDR (endpoint detection and response) and Managed Security Awareness Training (SAT) for MSPs. By integrating Huntress with MSPortal.ai, you can:

Link Huntress agents to devices for endpoint security coverage tracking
View escalations and incident reports on the Security page
Include Huntress summary reports in client reporting
Sync Managed SAT learners, training assignments, and phishing campaign results
Track security awareness training progress per user and per company

Prerequisites

Active Huntress account with API access
MSPortal.ai account with integration management permissions
Huntress API key pair (public and private key)
For Managed SAT: a separate Managed SAT (Curricula) client ID and secret. Your EDR API keys do not work for SAT

Part 1: Generate Huntress API Keys

Before connecting to MSPortal.ai, create an API key pair in Huntress.

Log into Huntress

Access your Huntress dashboard at huntress.io.

Open API Credentials

Click your account name in the top-right corner and select API Credentials.

Create API Key

Click Setup (or Generate New API Key if you have created keys before) and give the key a descriptive name such as MSPortal Integration.

Copy Both Keys

Huntress generates a public key and a private key. Copy both immediately.

Store the private key securely! Huntress only shows the private key once. If you lose it, you’ll need to generate a new key pair.

If you plan to sync Managed SAT training data, you will also need Curricula OAuth credentials (client ID and client secret). You enter these on the wizard’s Connect step, right below the EDR keys. Contact Huntress support if you don’t have SAT API credentials for your account.

Part 2: MSPortal Setup Wizard

MSPortal.ai provides a guided wizard to connect and configure your Huntress integration:

Connect - Add EDR API keys and, optionally, Managed SAT credentials
Sync - Choose data sets
Map Organizations - Link Huntress EDR organizations to companies
SAT accounts - Link Managed SAT accounts to companies (appears only when Managed SAT is enabled)
Import Agents - Create device coverage

Starting the Wizard

Navigate to Integrations

In MSPortal.ai, go to Settings > Integrations.

Find Huntress

Locate the Huntress row in the list of available integrations.

Start Setup

Click Configure to launch the setup wizard.

Step 1: Connect

Enter your Huntress API credentials to establish the connection. If you use Managed SAT, enter its credentials on this same step.

Enter API Details

Fill in the connection fields:

Field	Value
API URL	`https://api.huntress.io/v1` (pre-filled; only change this if Huntress support directs you to)
Public API key	The public key from Part 1
Private API key	The private key from Part 1

Your API keys are stored securely using encrypted vault storage. They are never exposed in logs or API responses.

Test Connection

Click Test Connection to verify your credentials.A green “Connected to [account name]” message appears when the test passes.If the connection fails:

Verify both keys were copied in full without extra spaces
Ensure the key pair has not been revoked in Huntress
Confirm the API URL is https://api.huntress.io/v1

Enable Managed SAT (Optional)

If you use Huntress Managed SAT, turn on Enable Managed SAT in the Managed SAT card below the EDR fields.

Fill in the Curricula API credentials:

Field	Value
SAT client ID	Your Curricula OAuth client ID
SAT client secret	Your Curricula OAuth client secret
SAT API URL	`https://mycurricula.com/api/v1` (pre-filled)
SAT token URL	`https://mycurricula.com/oauth/token` (pre-filled)

Click Test SAT Connection to verify the credentials. Turning on the switch and testing do not save anything yet.

Connect Huntress

Once the connection test passes, click Connect Huntress to save your credentials (including SAT, if enabled), then click Next.If the EDR connection saves but SAT fails, reopen the saved connection and fix SAT there. Do not start a second Huntress connection.

Step 2: Sync

Choose which Huntress datasets MSPortal syncs. The switches on this step are drafts until you click Save Sync Settings. Next does not save them.

Managed EDR

Toggle the EDR datasets you want to sync:

Option	Description
Organizations	Company mapping source for Huntress EDR data
Agents	Device coverage source
Escalations and incident reports	Security page source
Summary reports	Reports page source
Auto-import mapped agents	Creates devices from mapped Huntress agents during sync (off by default)

Leave Auto-import mapped agents off during initial setup. You can review and import agents manually in Step 4, then enable auto-import once you’re confident in your organization mappings.

Managed SAT (Optional)

If you enabled Managed SAT on the Connect step, choose which SAT datasets to sync:

Option	Description
SAT accounts	Curricula account inventory used for SAT company mapping
SAT learners	User-level training status and learner profile data
SAT assignments	Training assignments, episodes, preview links, assignment learners, and learner activity
SAT phishing	Phishing campaigns and learner attempts
SAT reports	Managed SAT account summary reports

Click Save Sync Settings, then click Next.

Step 3: Map Organizations

Map Huntress organizations to your MSPortal companies. This determines which data syncs to which company.

Sync Organizations

If no organizations appear, click Sync Organizations to fetch organizations from your Huntress account.

The initial sync runs in the background. Check back after a few minutes if organizations don’t appear immediately.

Use Quick Match

Click Quick Match to automatically match Huntress organizations to MSPortal companies based on name similarity. Quick Match fills in the matches as pending links. Review them, adjust as needed, then click Import Selected to save them.

Manual Mapping

For organizations that weren’t automatically matched:

Find the organization in the list
Click the Select company… dropdown in the Mapped column
Search for and select the correct MSPortal company
If the company does not exist yet, use Create new company to add it and link it in one step
Click Import Selected to save the pending links

A company you create here is saved immediately. To remove a saved mapping, click the X button next to the company badge. The removal takes effect immediately.

Proceed

Once your organizations are mapped, click Next to continue. Next also saves any pending links.

Only data from mapped organizations syncs to MSPortal. Unmapped organizations are skipped.

Step 4: SAT Accounts (Managed SAT only)

If you enabled Managed SAT, the wizard adds a SAT accounts step after Map Organizations. Mapping an EDR organization does not map its SAT account, so map each one here.

Map Each SAT Account

Map each Curricula account to its MSPortal company the same way as the organizations, using Quick Match or the Select company… dropdown.

Save and Continue

Click Import Selected or Next to save the links. Check that each company’s EDR organization and SAT account point to the same company.

Step 5: Import Agents

Review synced data and link Huntress agents to devices.

Review Sync Stats

The Import step shows counts for each synced data type:

Organizations
Agents
Escalations
Incidents
Reports

The “Last synced” timestamp shows when data was last updated.

Sync Huntress Data

Click Sync Huntress Data to trigger a full background sync of all enabled datasets. Depending on your data volume, this may take several minutes.

Import Agents as Devices

Click Import Agents as Devices to open the agent import page. Opening the page does not import anything.Huntress agents link to existing MSPortal devices first. Only an agent that cannot be safely matched by Huntress identity, serial number, MAC address, or hostname in the mapped company creates a new device.The import page shows:

Status	Meaning
Linked to devices	Agents already attached to a MSPortal device
Ready to link or create	Agents that can be imported now
Need company mapping	Agents whose organization isn’t mapped yet
Ignored	Agents you’ve excluded from import

Use Import Selected or Import All Mapped to link agents. Both link to existing devices first and only create new devices for unmatched agents.

Set up device type mappings before importing so brand-new devices get the right device type. The import page warns you if any Huntress types still need a mapping.

See Import Devices for the import controls.

Complete Setup

Click Complete Setup to return to the Integrations page. Syncs may still be running. Check the Devices, Security and Training pages afterward. An Agents count does not mean every agent is linked to a device.

What Gets Synced

Managed EDR

Data Type	Description
Organizations	Huntress organizations used for company mapping
Agents	Endpoint agents with hostname, OS, serial, and MAC details
Escalations	Security escalations raised by Huntress analysts
Incident Reports	Detailed incident reports for detected threats
Summary Reports	Periodic account and organization summary reports

Managed SAT

Data Type	Description
SAT Accounts	Curricula accounts used for SAT company mapping
Learners	User-level training status and learner profiles
Assignments	Training assignments and per-learner activity
Phishing	Phishing campaigns and learner attempt results
SAT Reports	Managed SAT account summary reports

Where the Data Appears

Data	Where to find it
Managed EDR agents	The Devices page, alongside the rest of your device inventory
Managed SAT assignments	Training > Security Training > Assignments
Managed SAT learner progress	Training > Security Training > Training Status, next to your other awareness providers
Your own assigned episodes	Training > Course Library, as course tiles counted with the rest of your training
Awareness metrics in reports	The Security Awareness blocks and the Security Awareness & Training source on QBR and security review reports

See Security Awareness Training for how to work with assignments, learner progress, and reporting.

Managed SAT data only appears for Huntress organizations mapped to an MSPortal company. Unmapped organizations are skipped by the sync.

Synchronization Schedule

After initial setup, all enabled datasets sync automatically once per day. You can trigger a manual sync at any time from the wizard’s Import step using Sync Huntress Data.

Only datasets enabled and saved on the Sync step are synced. Data from unmapped organizations is skipped.

Managing Your Integration

After setup, manage your integration from Settings > Integrations:

Action	Description
Configure	Re-open the wizard to modify settings or add more mappings
Resync	Trigger a full data refresh
Disconnect	In the row’s actions menu. Removes the integration and its stored credentials. It does not uninstall Huntress agents

Updating Your API Keys

Open Integration Settings

Go to Settings > Integrations and click Configure on the Huntress card.

Enter New Keys

On the Connect step, enter your new public and private keys. Saved keys show masked, and Test Connection stays disabled until you type the actual private key.

Test and Save

Click Test Connection, then Save Connection.

To turn Managed SAT on or off later, change Enable Managed SAT on the Connect step and click Save Connection. SAT dataset choices still save separately with Save Sync Settings.

Adding More Organization Mappings

As you onboard new clients in Huntress:

Open the Map Step

Open the wizard and click Map Organizations in the stepper.

Sync and Map

Click Sync Organizations to fetch new organizations, then use Quick Match or manual mapping to connect them to companies.

Troubleshooting

Issue	Solution
Connection test fails	Verify both API keys are correct and the key pair hasn’t been revoked in Huntress
SAT connection test fails	Confirm the client ID and secret are valid Curricula OAuth credentials, not your EDR keys
EDR works but SAT data is missing	Confirm Enable Managed SAT is on and saved on the Connect step, the SAT datasets are saved on the Sync step, and the SAT accounts are mapped
Test Connection is disabled	The saved key is masked. Type the actual key to run a fresh test
Sync choices reverted	Click Save Sync Settings before leaving the Sync step
No organizations appear	Click Sync Organizations on the Map Organizations step and wait a few minutes
Agents not creating devices	Check that the agent’s organization is mapped to a company and device type mappings are set
Duplicate devices	Agents link to existing devices by identity, serial, MAC, or hostname first; verify the existing device belongs to the mapped company
Data not syncing	Ensure the dataset is enabled and saved on the Sync step and the organization is mapped
Security counts are zero	Check that the security dataset is enabled, the organization is mapped and a sync has finished. Zero does not prove there are no threats
Stale data	Use “Sync Huntress Data” on the Import step to trigger a manual refresh

Security & Privacy

API Key Storage: Your Huntress and Curricula credentials are encrypted using vault storage and never exposed in logs or responses
Data Isolation: All synced data is tenant-isolated and only visible to your organization
Read-Only Access: MSPortal only reads data from Huntress; it never modifies your Huntress configuration

Next Steps

After setting up the Huntress integration:

View Security Data

Explore escalations and incident reports

Manage Devices

Review imported Huntress agents on the Devices page

Security Awareness Training

Track Managed SAT assignments, learner progress, and phishing results

Huntress Assignments

Review Managed SAT training assignments

Build Reports

Include Huntress security data in client reports

Other Integrations

Explore additional integration options

Need Help?

For assistance with the Huntress integration, contact support@msportal.ai.

Getting Started

Service Delivery

Overview & Planning

MSP Tools

Administration

Connect your tools

Overview

Prerequisites

Part 1: Generate Huntress API Keys

Part 2: MSPortal Setup Wizard

Starting the Wizard

Step 1: Connect

Step 2: Sync

Managed EDR

Managed SAT (Optional)

Step 3: Map Organizations

Step 4: SAT Accounts (Managed SAT only)

Step 5: Import Agents

What Gets Synced

Managed EDR

Managed SAT

Where the Data Appears

Synchronization Schedule

Managing Your Integration

Updating Your API Keys

Adding More Organization Mappings

Troubleshooting

Security & Privacy

Next Steps

View Security Data

Manage Devices

Security Awareness Training

Huntress Assignments

Build Reports

Other Integrations

Need Help?

​Overview

​Prerequisites

​Part 1: Generate Huntress API Keys

​Part 2: MSPortal Setup Wizard

​Starting the Wizard

​Step 1: Connect

​Step 2: Sync

​Managed EDR

​Managed SAT (Optional)

​Step 3: Map Organizations

​Step 4: SAT Accounts (Managed SAT only)

​Step 5: Import Agents

​What Gets Synced

​Managed EDR

​Managed SAT

​Where the Data Appears

​Synchronization Schedule

​Managing Your Integration

​Updating Your API Keys

​Adding More Organization Mappings

​Troubleshooting

​Security & Privacy

​Next Steps

View Security Data

Manage Devices

Security Awareness Training

Huntress Assignments

Build Reports

Other Integrations

​Need Help?

Overview

Prerequisites

Part 1: Generate Huntress API Keys

Part 2: MSPortal Setup Wizard

Starting the Wizard

Step 1: Connect

Step 2: Sync

Managed EDR

Managed SAT (Optional)

Step 3: Map Organizations

Step 4: SAT Accounts (Managed SAT only)

Step 5: Import Agents

What Gets Synced

Managed EDR

Managed SAT

Where the Data Appears

Synchronization Schedule

Managing Your Integration

Updating Your API Keys

Adding More Organization Mappings

Troubleshooting

Security & Privacy

Next Steps

Need Help?