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 Curricula OAuth client ID and secret
Part 1: Generate Huntress API Keys
Before connecting to MSPortal.ai, create an API key pair in Huntress.1
Log into Huntress
Access your Huntress dashboard at huntress.io.
2
Open API Credentials
Click your account name in the top-right corner and select API Credentials.
3
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.4
Copy Both Keys
Huntress generates a public key and a private key. Copy both immediately.
If you plan to sync Managed SAT training data, you will also need Curricula OAuth credentials (client ID and client secret). These are configured later in the wizard’s Configure Sync step. Contact Huntress support if you don’t have SAT API credentials for your account.
Part 2: MSPortal Setup Wizard
MSPortal.ai provides a guided 4-step wizard to connect and configure your Huntress integration:- Connect - Add API keys
- Configure Sync - Choose data sets
- Map Organizations - Link Huntress to companies
- Import Agents - Create device coverage
Starting the Wizard
1
Navigate to Integrations
In MSPortal.ai, go to Settings > Integrations.
2
Find Huntress
Locate the Huntress integration card in the list of available integrations.
3
Start Setup
Click Configure to launch the setup wizard.
Step 1: Connect
Enter your Huntress API credentials to establish the connection.1
Enter API Details
Fill in the connection fields:
Your API keys are stored securely using encrypted vault storage. They are never exposed in logs or API responses.
2
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
3
Connect Huntress
Once the connection test passes, click Connect Huntress to save your credentials and proceed.
Step 2: Configure Sync
Choose which Huntress datasets MSPortal syncs.Managed EDR
Toggle the EDR datasets you want to sync:Managed SAT (Optional)
If you use Huntress Managed SAT, enable the Managed SAT toggle and enter your Curricula API credentials:
Click Test SAT Connection to verify the credentials, then choose which SAT datasets to sync:
Click Save Sync Settings to continue.
Step 3: Map Organizations
Map Huntress organizations to your MSPortal companies. This determines which data syncs to which company.1
Sync Organizations
If no organizations appear, click Sync 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.
2
Use Quick Match
Click Quick Match to automatically match Huntress organizations to MSPortal companies based on name similarity. Review the results and adjust as needed.
3
Manual Mapping
For organizations that weren’t automatically matched:
- Find the organization in the list
- Click the Select company dropdown in the “Mapped To” column
- Search for and select the correct MSPortal company
4
Map SAT Accounts
If you enabled Managed SAT, a second mapping table appears for SAT accounts. Map each Curricula account to its MSPortal company the same way.
5
Proceed
Once your organizations are mapped, click Next to continue.
Step 4: Import Agents
Review synced data and link Huntress agents to devices.1
Review Sync Stats
The Import step shows counts for each synced data type:
- Organizations
- Agents
- Escalations
- Incidents
- Reports
2
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.
3
Import Agents as Devices
Click Import Agents as Devices to open the agent import page.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:
Use Import Selected or Import All Mapped to link agents. Both link to existing devices first and only create new devices for unmatched agents.
What Gets Synced
Managed EDR
Managed SAT
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 in the Configure Sync step are synced. Data from unmapped organizations is skipped.
Managing Your Integration
After setup, manage your integration from Settings > Integrations:Updating Your API Keys
1
Open Integration Settings
Go to Settings > Integrations and click Configure on the Huntress card.
2
Enter New Keys
On the Connect step, enter your new public and private keys.
3
Test and Save
Click Test Connection, then Save Connection.
Adding More Organization Mappings
As you onboard new clients in Huntress:1
Open the Map Step
Open the wizard and click Map Organizations in the stepper.
2
Sync and Map
Click Sync to fetch new organizations, then use Quick Match or manual mapping to connect them to companies.
Troubleshooting
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
Build Reports
Include Huntress security data in client reports
Other Integrations
Explore additional integration options