Huntress Ships More API Than Its Native Integrations Use. A Custom Connector Unlocks the Rest
TL;DR
- The Huntress API exposes endpoints well beyond what the native PSA integrations consume, including incident, agent, and subscription data.
- A Power Automate custom connector authenticates to Huntress with Basic Authentication, using the API key as the username label and the API secret as the password label.
- Most Huntress API endpoints return multiple pages, so adding a page parameter to each connector definition saves rework once flows hit real data volumes.
- Custom connectors require a premium Power Platform license, which Silver and Gold Microsoft partner benefits often already include as of September 2022.
- A 200 response on the connector's Test tab confirms credentials and definitions before any flow gets built on top.
The native Huntress integrations cover the obvious ground: subscription information written to your PSA's agreements and contracts, tickets created when new incidents occur. Useful, but fixed. The Huntress API (opens in new tab) exposes far more than those integrations consume, and Power Automate's custom connector feature turns it into a building block you can drop into any flow.
A few reasons you would want this wired up:
- Chain more automation around the moment an incident occurs
- Push subscription information to third-party tools Huntress does not integrate with natively as of September 2022, like QuickBooks
- Aggregate subscription and device information across vendors
That last one is where we get the most value. Here is a Power BI report fed by the connector that shows device information across vendors, built to answer a simple question: do the device counts reported by Intune, the RMM, and Huntress actually agree?
The same report pulls in subscription information so it can be aggregated at the customer level:
Disparities between what your security tooling thinks it covers and what your management tooling thinks exists are exactly the kind of thing nobody spots by hand.
What you need before you start
- API credentials from Huntress. In the Huntress portal, go to API Credentials to generate an API key and API secret.
- A premium Power Platform subscription. Licensing gets confusing here, but one of the following plans covers it, and your Silver or Gold Microsoft partnership may already include these licenses:
How do you build the connector?
- Go to https://make.powerautomate.com/ (opens in new tab) > Data > Custom Connectors > + New Custom Connector > Create from blank.
- Upload the Huntress logo if you like and add the host information:
- On the Security page, select Basic Authentication. Add the labels APIKey and APISecret. You are not entering your actual credentials on this page; these are just the labels the connection prompt will show later:
- Under Definitions, add each endpoint you want available in your flows:
Follow the API documentation to get each request URL right. You can add parameters too. At a minimum, add the page parameter so your flows can paginate; endpoints returning multiple pages is very common with this API.
How do you test it before building flows?
- Go to the Test tab and click + New Connection. This is where the actual Huntress API key and secret get entered:
- After the connection is saved you are redirected back to the Test page. Click the refresh button to load the connection you just created:
- Test the connection by selecting an operation and clicking Test Operation:
- A 200 response means the connector and credentials are working.
- Click Create Connector to save it.
- From now on, when you build a flow, Huntress appears as an option under Custom, with every endpoint you defined ready to use:
Where to take it from here
The same connector pattern pairs naturally with distributor data; we cover connecting the Pax8 API in Power Automate in a separate walkthrough, and the two together feed the cross-vendor reporting shown above. For the full video tutorial of this build, watch the YouTube walkthrough (opens in new tab) and leave any questions in the comments there.
Frequently asked questions
Does using the Huntress API cost anything extra?
No. You generate an API key and secret free of charge under API Credentials in the Huntress portal. The only licensing cost sits on the Microsoft side, where custom connectors are a premium Power Platform feature.
Why add a page parameter to the connector definitions?
Most Huntress endpoints paginate their responses, which is very common with this API. Defining the page parameter up front lets your flows loop through every page instead of silently processing only the first one.
Does this pattern work for other vendors in the MSP stack?
Yes. Any vendor API that supports Basic Authentication can become a custom connector the same way. APIs that use client credentials grants, like Pax8's, need a different approach with HTTP actions inside the flow itself.
Automate the busywork, then verify the posture
Connecting your security stack is half the job; proving every tenant is actually configured well is the other half. CloudCapsule checks 250+ Microsoft 365 controls per tenant in about 60 seconds.
Run a free scan
Written by
Nick Ross
CEO · Microsoft MVP · Founder, T-Minus 365
Nick is not just a CEO, he's a respected thought leader and influencer in the MSP space. Tens of thousands of MSPs learn through his YouTube channel, T-Minus365. Nick has been honored as a three-time Microsoft MVP for his educational content; his expertise and influence are the backbone of our mission, ensuring that you are in the best hands when it comes to security.
Nick joined Pax8 in 2017, where he would ultimately oversee product management for PSA and Microsoft integrations. Following his tenure at Pax8, Nick has continued to demonstrate his leadership prowess as an executive at various MSPs, culminating in his most recent role at Sourcepass.
Nick holds a Bachelor's Degree in Business Management from Florida State University, as well as a Minor Degree in Entrepreneurship. In his free time, Nick is an avid hiker, reader, and fitness-junkie.
