# ResultsIQ Control Center docs, in full > Every page of the ResultsIQ Control Center docs in one file, for AI assistants. The docs index is at https://www.resultsiq.ai/docs/llms.txt and each page is also at its own address, ending in index.md. ## For AI assistants helping an MSP onboard - Use only these docs and each vendor’s own API docs. Say when they don’t cover something, and don’t guess. - Ask which tools the MSP runs and match each one to Every tool below. If one isn’t listed, say so: the MSP can send its API docs to connor.reece@resultsiq.ai. - For each tool, give what the vendor needs and the link to its API docs, and flag plan requirements and partner access. - Never ask for passwords, API keys or other secrets. The MSP enters them in Control Center, where they’re kept in its vault, not in a chat. - Link each tool to its docs page, so the MSP can check it. --- Page: https://www.resultsiq.ai/docs/ # Control Center docs Everything you need to get started with ResultsIQ Control Center: onboarding, how it works, how it’s secured, and what it needs from each tool you run. Read it here, or point your AI at it. ## Start here - [Onboard with your AI](https://www.resultsiq.ai/docs/ai/): One prompt turns ChatGPT, Claude or Copilot into your onboarding guide, working from these docs. - [Your first 90 days](https://www.resultsiq.ai/docs/onboarding/): What happens from setup to your first client’s invoice, and what to have ready. - [How connections work](https://www.resultsiq.ai/docs/connections/): How Control Center reaches your tools, and what to have before you connect one. - [Every tool](https://www.resultsiq.ai/docs/tools/): 159 tools, each with what Control Center uses, what the vendor needs and its API docs. ## The platform - [What Control Center does](https://www.resultsiq.ai/docs/platform/): Nine capabilities, from client business context to billing and AI margin. - [Control Center MCP](https://www.resultsiq.ai/docs/mcp/): Your team’s Claude or ChatGPT, connected to every client and tool. - [Security and data](https://www.resultsiq.ai/docs/security/): Where it runs, what stays yours, and where SOC 2 stands. - [Pricing and terms](https://www.resultsiq.ai/docs/pricing/): What it costs, the 90 days, and the terms after them. - [FAQ](https://www.resultsiq.ai/docs/faq/): The questions MSP owners ask about Control Center. ## For AI assistants The docs are published as plain text too, so the AI your team uses reads the same source you do. - [llms-full.txt](https://www.resultsiq.ai/docs/llms-full.txt): Every page of the docs in one file. Point your AI here. - [llms.txt](https://www.resultsiq.ai/docs/llms.txt): The index: every page, with a line on each. - index.md: Any page as Markdown: add index.md to its address, or use Copy page at the top of the page. [How to onboard with your AI](https://www.resultsiq.ai/docs/ai/) ## Need a hand? Book a 30-minute call with Connor Reece, or email [connor.reece@resultsiq.ai](mailto:connor.reece@resultsiq.ai). Using a tool that isn’t listed? Send us a link to its API docs. [Book a call](https://www.resultsiq.ai/demo/?src=docs) [Join the waitlist](https://www.resultsiq.ai/waitlist/) --- Page: https://www.resultsiq.ai/docs/ai/ # Onboard with your AI Give ChatGPT, Claude or Copilot one prompt and it becomes your onboarding guide: it asks which tools you run, tells you what each vendor needs, and takes you through them one at a time, all from these docs. ## The prompt Paste it into the AI your team already uses, or open it in ChatGPT, Claude or Copilot from here. ``` Read https://www.resultsiq.ai/docs/llms-full.txt . It's the ResultsIQ Control Center docs: onboarding, security, and what Control Center needs from every tool it connects to. My MSP is onboarding onto Control Center. Be our onboarding guide: 1. Ask me which tools we run (PSA, RMM, endpoint security, backup, documentation, Microsoft 365 and the rest). Match each one to its page in the docs, and tell me if one isn't there. 2. Give me a checklist: what to have ready for our first 90 days, then one line per tool with what we need from that vendor and the link to its API docs. Flag anything that needs a certain plan or the vendor's approval. 3. Then take me through it one tool at a time. Tell me exactly what to do, and wait for me before moving on. Use only these docs and each vendor's own API docs, and say when they don't cover something. Never ask me for passwords or API keys: we enter those in Control Center, not in this chat. ``` Use an AI that can read web pages. If yours can’t, [download llms-full.txt](https://www.resultsiq.ai/docs/llms-full.txt) and attach it to the chat with the prompt. ## What happens next - It reads the docs. One file, llms-full.txt, with every page of these docs, including each tool’s requirements and the link to its API docs. - It asks which tools you run. Your PSA, RMM, security, backup, documentation, Microsoft 365 and the rest. It matches each one to its page, and tells you if one isn’t listed. - It gives you a checklist. What to have ready for your first 90 days, then one line per tool: what that vendor needs and where its API docs are. - It takes you through each tool. One at a time, from these docs and the vendor’s own, waiting for you before the next step. ## One source of truth Your AI reads the same pages you do, so what it tells your team matches what we tell you. For anything about a vendor’s own API, that vendor’s docs are the final word, and every tool page links to them. - [/docs/llms-full.txt](https://www.resultsiq.ai/docs/llms-full.txt): Every page of the docs in one file. This is what the prompt reads. - [/docs/llms.txt](https://www.resultsiq.ai/docs/llms.txt): The index: every page, with a line on each. - index.md: Any page as Markdown. Add index.md to its address, for example [/docs/tools/hudu/index.md](https://www.resultsiq.ai/docs/tools/hudu/index.md), or use Copy page at the top of the page. ## Keep keys out of the chat Your AI helps you find and create the access each tool needs. You enter API keys and passwords in Control Center, where they’re kept in its vault. Don’t paste them into a chat with any AI, and the prompt tells your AI not to ask for them. ## One tool at a time Every tool page has its own prompt, for when you only need one. Find the tool in [Every tool](https://www.resultsiq.ai/docs/tools/) and use Connect it with your AI. --- Page: https://www.resultsiq.ai/docs/onboarding/ # Your first 90 days From first call to first invoice. We set Control Center up with you, on a call every week or two, at your pace. ## The path - Talk with us. Book a 30-minute call with Connor Reece, or join the waitlist. We’re running pilots with select MSPs now and start reaching out to the waitlist in Q1 2027. - Days 1–45: your own MSP. Your own MSP first, not a client’s. - Set up with us - Your internal AI roadmap - First automations running - Days 46–90: your first client. One client, documented, scoped and priced, then live. - Their business documented - Their AI roadmap built - Billed for an AI service - Day 91: our first invoice. You’ve already been billing your client. If it’s working, you move to an annual contract with a 30-day notice period. If it isn’t, you walk away and owe nothing. The plan is our suggestion. Use the 90 days however works best for your MSP. ## What to have ready - Your AI account: Control Center runs on your own AI provider account and keys, at your own negotiated rate. Every token bills to you directly, and we add nothing. - Your team’s roles: Control Center’s roles are Owner/Admin, vCIO, Centralized Services, Service Desk and Billing. Each person sees only their clients and what their role allows. - Admin access to your tools: For each tool you’ll connect: an admin sign-in, a plan that includes API access, and permission to create an API key or register an app. See [How connections work](https://www.resultsiq.ai/docs/connections/). - Your first client: Days 46–90 run with one client, so have one in mind. ## What it costs Nothing for the first 90 days: no card, no contract and no procurement cycle. After day 90 it’s $1,750 a month for the platform, plus $75 a month for each workflow you bill a client for, on an annual contract with a 30-day notice period. See [Pricing and terms](https://www.resultsiq.ai/docs/pricing/). ## Let your AI help The onboarding prompt turns ChatGPT, Claude or Copilot into a guide for all of this, from these docs: what to have ready, then every tool you run, one at a time. [Onboard with your AI](https://www.resultsiq.ai/docs/ai/) --- Page: https://www.resultsiq.ai/docs/platform/ # What Control Center does Control Center is the platform MSPs use to scope, price, build and bill AI managed services across the clients they already have. It does nine things. ## Client business context Every client’s business documented and kept current. Every answer starts from it. - Techs work every ticket with the client’s business in view. - No interviews to run and no wiki to keep current. - New AI opportunities show up on their own. How it works: Control Center reads each client's apps and maps how their business runs, then every desk in your MSP works from that one record. [Client business context on the Capabilities page](https://www.resultsiq.ai/capabilities/#c-doc) ## AI managed services Find, value, price, build and bill AI services for every client. - AI finds, values, prices, builds and bills each service. - Your team makes one decision: approve it. - New recurring revenue on every client, at your margin. How it works: AI finds the opportunity, values it, prices it, builds it and bills it. The MSP approves it once. [AI managed services on the Capabilities page](https://www.resultsiq.ai/capabilities/#c-rev) ## Automation Build a workflow once and run it for every client, with approvals and a run log. - Build it once and sell it to every client. - No automation engineer to hire. - Tested on live data before any client sees it. How it works: Describe the job in plain English, AI drafts the workflow, it is tested on live data, and every client gets it. [Automation on the Capabilities page](https://www.resultsiq.ai/capabilities/#c-auto) ## Technology standards Your standard on every client, checked every morning, with drift flagged. - Problems get fixed before the client calls. - Junior engineers deliver like your senior ones. - Every gap becomes a project you can sell. How it works: Your standard is checked against every client each morning. Drift becomes a ticket you fix today or a project you sell. [Technology standards on the Capabilities page](https://www.resultsiq.ai/capabilities/#c-std) ## Reports and QBRs Reports and QBRs from live data, in each client’s terms, on demand. - QBRs ready in minutes, not days. - Every client gets one, every quarter. - Risks explained in business terms, with the fix priced. How it works: Live data from every tool and the client's business context become a QBR in their terms. Your vCIO approves it and sells the next project. [Reports and QBRs on the Capabilities page](https://www.resultsiq.ai/capabilities/#c-rep) ## Roadmaps and budgets A priced roadmap and budget for every client, refreshed every QBR. - A 12-month plan and budget for every client. - Clients see every cost coming. - AI spend alerts at 80%, and runs never stop. How it works: Approved work goes on a dated roadmap and a 12-month budget, and AI spend is tracked against the budget you sold. [Roadmaps and budgets on the Capabilities page](https://www.resultsiq.ai/capabilities/#c-road) ## Billing and AI margin Every AI run metered and priced, billed through your PSA at your margin. - AI services bill themselves, with zero labor hours. - See the margin on every client and every workflow. - Waste is found and fixed, so your margin grows. How it works: Every AI run is metered. Your cost plus your margin sets the price, and the line lands on the invoice in your PSA. [Billing and AI margin on the Capabilities page](https://www.resultsiq.ai/capabilities/#c-cost) ## Control Center MCP Your team’s AI on every client, every tool and every API. - Answers about any client, across every tool, in seconds. - Any answer can become an automation. - Same permissions as the login, and a person approves every action. How it works: Your tech asks in Claude or ChatGPT. Control Center MCP checks their role and clients, reaches every tool and answers with the source. [Control Center MCP in the docs](https://www.resultsiq.ai/docs/mcp/) ## Security and governance Role-based access, approvals and an audit trail for every AI run. - Your AI account and keys, and nothing trains on client data. - You decide exactly what AI can touch. - An audit trail for every action, ready for any auditor. How it works: An AI agent asks to act, your policy decides, a person approves anything risky, and every action is logged with its cost. [Security and governance on the Capabilities page](https://www.resultsiq.ai/capabilities/#c-sec) --- Page: https://www.resultsiq.ai/docs/mcp/ # Control Center MCP Your team connects Claude or ChatGPT to Control Center once and reaches every client tenant and connected tool, with the same roles and client scopes as their login. Included in the platform price. ## How it works Your team's Claude or ChatGPT connects to Control Center's MCP server once. Every question is checked against the person's role and assigned clients, and logged. From there it reaches the tools the MSP already uses, for every client: the PSA (tickets, agreements and time), the RMM (devices, patches and alerts), Microsoft 365 (users, licenses and sign-ins), endpoint security, backup, documentation and the rest, 156 tools in all, plus any REST API. ## What is MCP? The Model Context Protocol, the open standard Claude and ChatGPT use to work with other software. Control Center runs an MCP server, so your team’s AI can use your clients’ tools the way your team does. ## Which AI does it work with? Claude and ChatGPT at launch, on your own AI account at your own rate. We don’t mark it up. ## What does it cost? It’s included in Control Center’s $1,750 a month, with nothing per seat or per technician. ## Can every technician see every client? No. Each person signs in with their role from Control Center and sees only their clients and what that role allows. Service Desk and Engineers never see prices or margins. ## Can it change things in our tools? Only the actions an Owner or Admin turns on for each tool, with MFA, and only for roles allowed to use them. Every action is logged with who asked for it. ## Where do the passwords and API keys live? In Control Center’s vault. The AI never sees a password or API key, and nothing is pasted into the chat. ## Does it train on our data? No. Your clients’ data is never used to train a model or improve anything outside your tenant. ## Can our clients use it? Yes, from Q2 2027, as MCP as a service. You connect each client’s Claude or ChatGPT to their own apps, with your name on it and the access you set, and bill it monthly. Until then, it’s for your own team. [Control Center MCP in detail](https://www.resultsiq.ai/mcp/), with example conversations for each role. --- Page: https://www.resultsiq.ai/docs/security/ # Security and data Control Center runs in a ResultsIQ-managed Azure environment, isolated per tenant. Here’s what that covers, and what it doesn’t. ## What stays yours - Your AI account, your keys, your rate: You bring the provider account and negotiate the rate. Every token bills to you directly, and we take no spread on it. - Your connections, scoped by you: Every integration is enabled per tenant with the exact API operations you allow, and nothing else. - Your client relationships: We never contact your clients. The brand, tenants and invoices are yours. - The application, hosted by us: Control Center runs in a ResultsIQ-managed Microsoft Azure environment, isolated per tenant. You stand nothing up. We host the application, and we don’t resell your AI. Many platforms bundle compute and take a margin on every token. Yours bills to your own account at your rate, with nothing added. Bring-your-own-cloud is on the roadmap and isn’t in the product yet. The backend is built for it, and we’ll update this page when it ships. For now, Control Center is hosted by us. ## Control and logging - Role-based permissions: Enforced per tenant. Your team sees what you decide they see. - A run-level audit trail on every artifact: Every document, price, workflow and approval is logged with who, when and on what input. - A human approval gate before any client sees anything: We left this step manual on purpose. - No training on your data: Your client documentation is never used to train a model or improve anything outside your tenant. ## Certifications - Microsoft Azure Where it runs : A ResultsIQ-managed Azure environment, isolated per tenant. Microsoft publishes Azure’s own SOC and ISO reports. - SOC 2 Type I In progress : Target Q1 2027. We’ll publish the report once we have it. - Bring your own cloud Roadmap : The architecture supports it, but it isn’t available at launch. ## For your security lead They’ll want the hosting model, the permission matrix and the audit trail. All three are open to them during the ninety days, at no cost, before you commit to anything. [Security in detail](https://www.resultsiq.ai/security/) --- Page: https://www.resultsiq.ai/docs/pricing/ # Pricing and terms What Control Center costs, how the 90 days work, and the terms after them. ## Key facts - Price: $1,750 a month for the platform, plus $75 a month for each billable workflow (a workflow the MSP bills a client for). No cost for the first 90 days. No fees per seat, per user, per client or per device. - The 90 days: They cost nothing, so an MSP starts ROI positive before it spends anything on AI. The suggested path is days 1–45 inside the MSP’s own business and days 46–90 with its first client, but the MSP can use the 90 days however it wants. The first ResultsIQ invoice comes on day 91. - After day 90: An annual contract with a 30-day notice period. An MSP that decides it isn’t a fit walks away by day 90 and owes nothing. - Control Center MCP: Included in the platform price. The MSP’s team connects Claude or ChatGPT once and reaches every client tenant and connected tool, with the same roles and client scopes as the login. The team uses it for service delivery, automations and reports; it drafts automations that a person approves before they run. MCP as a service for the MSP’s clients is planned for Q2 2027. - Your AI account: The MSP brings its own AI provider account and keys. ResultsIQ adds no markup on AI usage. - Hosting: Hosted by ResultsIQ in Microsoft Azure, isolated per tenant. SOC 2 Type I is in progress, with a target of Q1 2027. - Availability: ResultsIQ is running pilots with select MSPs and starts reaching out to the waitlist in Q1 2027. Book a call at [www.resultsiq.ai/demo/](https://www.resultsiq.ai/demo/) or join the waitlist at [www.resultsiq.ai/waitlist/](https://www.resultsiq.ai/waitlist/). - Who built it: Built by Connor Reece, President and CEO of Reboot, the MSP his father started in 2005. ## Terms and privacy The [Terms](https://www.resultsiq.ai/terms) and the [Privacy Policy](https://www.resultsiq.ai/privacy) cover the details. [Pricing](https://www.resultsiq.ai/pricing/) has the math behind the price, and [90 Days](https://www.resultsiq.ai/90-days/) has the plan. --- Page: https://www.resultsiq.ai/docs/faq/ # FAQ Questions MSP owners ask about Control Center and the 90 days. ## What does it cost? $1,750 a month for the platform, plus $75 a month for each workflow you bill a client for. Nothing for the first 90 days. ## When can we start? We’re running pilots with select MSPs now. In Q1 2027 we start reaching out to the waitlist. [Join the waitlist](https://www.resultsiq.ai/waitlist/) to be first in line. ## Do I need a card or a contract to start? No. No card, no contract and no procurement cycle. ## Do I need to hire anyone? No. We set it up with you, on a call every week or two at your pace. ## When does revenue start? By day 90 your first client is paying you for an AI service. You bill them before we bill you. ## What happens on day 91? If it’s working, you move to an annual contract with a 30-day notice period, and we send our first invoice. If it isn’t, you walk away. There’s nothing to cancel. ## Do I have to follow the 90-day plan? No. The 90 days are there so you start ROI positive before you spend anything on AI. The plan is our suggestion, so use the time however works best for your MSP. ## What if my team won’t use it? You’ll know by day 45, because the first 45 days run inside your own MSP, not a client’s. If it doesn’t stick there, you walk. ## Who pays for the AI? You do, on your own AI account, at your own negotiated rate. We never mark it up. ## Who owns the data? You do. Your data, your clients’ data and everything the platform produces stay yours, whether you stay with us or not. ## Where does it run? We host it in the ResultsIQ Azure environment. There’s nothing for you to stand up. ## What does it connect to? 156 MSP tools, plus anything with a documented REST API. [See the list](https://www.resultsiq.ai/docs/tools/). ## Is it SOC 2 certified? SOC 2 Type I is in progress, with a target of Q1 2027. [See where we stand](https://www.resultsiq.ai/docs/security/). ## What’s the biggest risk? Adoption. If you don’t have strategic conversations with your clients today, software won’t start them. Control Center makes those conversations faster and better evidenced. --- Page: https://www.resultsiq.ai/docs/connections/ # How connections work Control Center connects to each tool through the vendor’s own documented API, with access you grant and scope. Here’s how, and what to have before you connect a tool. ## Through the vendor’s own API Control Center works through the documented API each vendor publishes, using access you grant in that tool, such as an API key or an app you approve. ## Scoped per client Every integration is enabled per tenant with the exact API operations you allow, and nothing else. ## Logged, and approved by a person Every document, price, workflow and approval is logged with who, when and on what input. A person approves before any client sees anything. ## Keys stay in the vault API keys and passwords live in Control Center’s vault. Your team’s AI never sees them, and nothing is pasted into a chat. ## Your AI follows the same rules Your team reaches the same tools from Claude or ChatGPT through [Control Center MCP](https://www.resultsiq.ai/docs/mcp/), with the same roles and client scopes as their login. ## Before you connect a tool - An admin sign-in for the tool. - A plan that includes API access. A few vendors keep it to certain plans, and each tool’s page says so. - Permission to create an API key or register an app in the tool. - Your region or instance address, where the vendor uses one. Each tool’s page in [Every tool](https://www.resultsiq.ai/docs/tools/) lists what that vendor needs on top of this. ## Where each vendor’s API docs are - Public docs : Anyone can read the vendor’s API docs. - Docs need a login : You sign in with a customer or partner account to read them. - Partner access : The vendor opens its API through a partner or developer program, so the connection depends on the vendor’s approval. ## A tool that isn’t listed If it has a documented API, Control Center can connect to it. [Email us](mailto:connor.reece@resultsiq.ai?subject=API%20docs%20for%20a%20tool) the tool’s name and a link to its API docs. --- Page: https://www.resultsiq.ai/docs/tools/ # Every tool The 159 tools Control Center connects to, by category: what it uses from each, what the vendor needs, and the link to the vendor’s API docs. 156 connect today, and 3 depend on the vendor’s partner program. Public docs: anyone can read them. Docs need a login: a customer or partner login. Partner access: the vendor opens its API through a partner or developer program. ## PSA - [ConnectWise PSA](https://www.resultsiq.ai/docs/tools/cwpsa/): Uses: Tickets, agreements, billing and time entries. Needs: The docs need a ConnectWise Developer Network account, which ConnectWise approves. API docs: https://developer.connectwise.com/Products/ConnectWise_PSA (docs need a login). - [Autotask PSA](https://www.resultsiq.ai/docs/tools/autotask/): Uses: Tickets, agreements, billing and time entries. Needs: An API user created in Autotask. The API address depends on your Autotask zone. API docs: https://www.autotask.net/help/DeveloperHelp/Content/APIs/REST/REST_API_Home.htm (public docs). - [HaloPSA](https://www.resultsiq.ai/docs/tools/halo/): Uses: Tickets, agreements, billing and time entries. Needs: An API application registered in HaloPSA (client ID and secret). Addresses are specific to your instance. API docs: https://halopsa.com/apidoc (public docs). - [Kaseya BMS](https://www.resultsiq.ai/docs/tools/bms/): Uses: Tickets, agreements, billing and time entries. Needs: A BMS username, password and tenant. Use your region’s API: US, EMEA or APAC. API docs: https://help.bms.kaseya.com/help/Content/BMS%20API/bms-api-v2-bms-rest-apis.html (public docs). - [Syncro](https://www.resultsiq.ai/docs/tools/syncro/): Uses: Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. Needs: An API token from Admin > API Tokens. The address uses your Syncro subdomain. API docs: https://api-docs.syncromsp.com/ (public docs). - [SuperOps](https://www.resultsiq.ai/docs/tools/superops/): Uses: Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. Needs: An API token from your SuperOps profile settings, plus your SuperOps subdomain. API docs: https://developer.superops.com/ (public docs). - [Atera](https://www.resultsiq.ai/docs/tools/atera/): Uses: Tickets, agreements, time entries, devices, alerts and patching. Needs: The docs need an Atera login. The API key is under Admin > API and isn’t available during a trial. API docs: https://app.atera.com/apidocs (docs need a login). - [Accelo](https://www.resultsiq.ai/docs/tools/accelo/): Uses: Tickets, agreements and time entries. Needs: An API application registered under Configuration > API (OAuth 2.0). API docs: https://accelo.github.io/docs/ (public docs). - [ServiceNow](https://www.resultsiq.ai/docs/tools/servicenow/): Uses: Tickets. Needs: Your instance address and a user with roles for the tables it reads. API docs: https://www.servicenow.com/docs/r/api-reference (public docs). - [Freshservice](https://www.resultsiq.ai/docs/tools/freshservice/): Uses: Tickets and time entries. Needs: An API key from your profile settings. Rate limits depend on your plan. API docs: https://api.freshservice.com/ (public docs). - [Zendesk](https://www.resultsiq.ai/docs/tools/zendesk/): Uses: Tickets. Needs: Requests go to your own Zendesk subdomain. API docs: https://developer.zendesk.com/api-reference/ticketing/introduction/ (public docs). - [Jira Service Management](https://www.resultsiq.ai/docs/tools/jsm/): Uses: Tickets and time entries. Needs: An Atlassian account email and API token, against your site address. API docs: https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/ (public docs). ## RMM - [Syncro](https://www.resultsiq.ai/docs/tools/syncro/): Uses: Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. Needs: An API token from Admin > API Tokens. The address uses your Syncro subdomain. API docs: https://api-docs.syncromsp.com/ (public docs). - [SuperOps](https://www.resultsiq.ai/docs/tools/superops/): Uses: Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. Needs: An API token from your SuperOps profile settings, plus your SuperOps subdomain. API docs: https://developer.superops.com/ (public docs). - [Atera](https://www.resultsiq.ai/docs/tools/atera/): Uses: Tickets, agreements, time entries, devices, alerts and patching. Needs: The docs need an Atera login. The API key is under Admin > API and isn’t available during a trial. API docs: https://app.atera.com/apidocs (docs need a login). - [NinjaOne](https://www.resultsiq.ai/docs/tools/ninja/): Uses: Devices, alerts, patching, scripts and software inventory. Needs: An API client app (OAuth 2.0) created in NinjaOne. API docs: https://app.ninjaone.com/apidocs-beta/ (public docs). - [Datto RMM](https://www.resultsiq.ai/docs/tools/dattormm/): Uses: Devices, alerts, patching, scripts and software inventory. Needs: Turn on API access in Global Settings. Each user gets their own keys, and the address depends on your Datto RMM platform. API docs: https://rmm.datto.com/help/en/Content/2SETUP/APIv2.htm (public docs). - [ConnectWise Automate](https://www.resultsiq.ai/docs/tools/automate/): Uses: Devices, patching and scripts. Needs: The docs need a ConnectWise Developer Network account, which ConnectWise approves. API docs: https://developer.connectwise.com/Products/ConnectWise_Automate (docs need a login). - [ConnectWise RMM](https://www.resultsiq.ai/docs/tools/cwrmm/): Uses: Devices, patching and scripts. Needs: Regional API addresses for the US, EU and Australia, with OAuth 2.0 client credentials. API docs: https://openapi.service.itsupport247.net. - [Kaseya VSA](https://www.resultsiq.ai/docs/tools/vsa/): Uses: Devices, alerts, patching, scripts and software inventory. Needs: An administrator creates an API token. Requests go to your own VSA server address. API docs: https://api.vsax.net (public docs). - [N-able N-central](https://www.resultsiq.ai/docs/tools/ncentral/): Uses: Devices, alerts, patching, scripts and software inventory. Needs: An API-only user and its token, created in N-central. API docs: https://developer.n-able.com/n-central (public docs). - [N-able N-sight](https://www.resultsiq.ai/docs/tools/nsight/): Uses: Devices, alerts, patching, scripts and software inventory. Needs: An API key generated in N-sight. API docs: https://documentation.n-able.com/remote-management/userguide/Content/api_calls.htm (public docs). - [Level](https://www.resultsiq.ai/docs/tools/level/): Uses: Devices, alerts, patching and scripts. Needs: An API key from Settings > API keys, read-only or read-write. API docs: https://developers.level.io/ (public docs). - [Action1](https://www.resultsiq.ai/docs/tools/action1/): Uses: Devices, patching, scripts and software inventory. Needs: An API client ID and secret from Action1’s API Credentials page. API docs: https://www.action1.com/api-documentation/ (public docs). - [Pulseway](https://www.resultsiq.ai/docs/tools/pulseway/): Uses: Devices. API docs: https://api.pulseway.com/ (public docs). - [ImmyBot](https://www.resultsiq.ai/docs/tools/immy/): Uses: Devices, scripts and software inventory. Needs: A Microsoft Entra app registration. Each instance has its own API reference at your-subdomain.immy.bot/swagger. API docs: https://www.immy.bot/documentation/reference/api-documentation/ (public docs). - [Automox](https://www.resultsiq.ai/docs/tools/automox/): Uses: Devices, patching, scripts and software inventory. Needs: An API key from the Automox console. API docs: https://docs.automox.com/product/Developer/Developer_LP.htm (public docs). - [Microsoft Intune](https://www.resultsiq.ai/docs/tools/intune/): Uses: Devices, patching, scripts, software inventory and device compliance. Needs: An Intune license and a Microsoft Entra app with Microsoft Graph permissions. API docs: https://learn.microsoft.com/graph/api/resources/intune-graph-overview?view=graph-rest-1.0 (public docs). ## Endpoint security - [SentinelOne](https://www.resultsiq.ai/docs/tools/s1/): Uses: Threats, agent health, isolating devices and remediation. Needs: The API reference and API tokens are inside your SentinelOne management console. API docs: no public link (docs need a login). - [CrowdStrike Falcon](https://www.resultsiq.ai/docs/tools/crowdstrike/): Uses: Threats, agent health, isolating devices and remediation. Needs: A Falcon Administrator creates an API client (ID and secret) with the scopes it needs. API docs: https://developer.crowdstrike.com/api-reference/ (public docs). - [Huntress](https://www.resultsiq.ai/docs/tools/huntress/): Uses: Threats, agent health, isolating devices and remediation. Needs: A user-based API key from your Huntress account. Huntress has deprecated the older account-level key. API docs: https://api.huntress.io/docs (public docs). - [Microsoft Defender for Endpoint](https://www.resultsiq.ai/docs/tools/defender/): Uses: Threats, agent health, isolating devices and remediation. Needs: A Microsoft Entra app registration. Use your region’s API address. API docs: https://learn.microsoft.com/defender-endpoint/api/apis-intro (public docs). - [Sophos Central](https://www.resultsiq.ai/docs/tools/sophos/): Uses: Threats, agent health, isolating devices and remediation. Needs: A Super Admin creates API credentials in Sophos Central. Each tenant has its own data-region address. API docs: https://developer.sophos.com/ (public docs). - [Bitdefender GravityZone](https://www.resultsiq.ai/docs/tools/bitdefender/): Uses: Threats, agent health, isolating devices and remediation. Needs: An API key from your GravityZone account settings. API docs: https://www.bitdefender.com/business/support/en/77209-125277-public-api.html (public docs). - [ESET PROTECT](https://www.resultsiq.ai/docs/tools/eset/): Uses: Threats, agent health, isolating devices and remediation. Needs: Through ESET Connect, for ESET PROTECT Cloud, ESET Inspect and ESET Cloud Office Security. API docs: https://help.eset.com/eset_connect/en-US/index.html (public docs). - [ThreatDown](https://www.resultsiq.ai/docs/tools/threatdown/): Uses: Threats, agent health, isolating devices and remediation. Needs: A Global or Site Administrator creates an OAuth client (read, write or execute) under Integrate in OneView. API docs: https://support.threatdown.com/hc/en-us/articles/4413799441683 (public docs). - [Webroot](https://www.resultsiq.ai/docs/tools/webroot/): Uses: Threats, agent health and remediation. Needs: An API client ID and secret, which come from your Webroot representative. API docs: https://unityapi.webrootcloudav.com/Docs/en/APIDoc (public docs). - [Blackpoint Cyber](https://www.resultsiq.ai/docs/tools/blackpoint/): Uses: Threats. Needs: We couldn’t find public API docs. Ask Blackpoint for them. API docs: no public link (docs need a login). - [Arctic Wolf](https://www.resultsiq.ai/docs/tools/arcticwolf/): Uses: Threats. Needs: A personal API key from the Unified Portal. The Data Retrieval API needs a Data Explorer license. API docs: https://docs.arcticwolf.com/en/developer-and-oem/data-retrieval-api/arctic-wolf-data-retrieval-api/use-the-data-retrieval-api (public docs). - [Cynet](https://www.resultsiq.ai/docs/tools/cynet/): Uses: Threats, agent health and remediation. API docs: https://help.api.cynet.com/docs/API-V3/9g00cv3m8b10g-cynet-api-documentation (public docs). - [Datto EDR](https://www.resultsiq.ai/docs/tools/dattoedr/): Uses: Threats, agent health and remediation. Needs: The API explorer is inside each customer’s own Datto EDR instance. API docs: https://edr.datto.com/help/Content/2-manage/api-loopback-explorer.html (docs need a login). Note: Datto EDR’s API explorer is inside each customer’s own Datto EDR instance. ## SIEM and managed SOC - [Microsoft Sentinel](https://www.resultsiq.ai/docs/tools/sentinel/): Uses: Alerts, incidents and log search. Needs: A Microsoft Entra app with a Microsoft Sentinel role on the workspace. Log search runs through the Azure Monitor Logs API. API docs: https://learn.microsoft.com/en-us/rest/api/securityinsights/ (public docs). - [Blumira](https://www.resultsiq.ai/docs/tools/blumira/): Uses: Alerts, incidents and agent health. Needs: Its MSP endpoints cover every client account you manage. API docs: https://support.blumira.com/hc/en-us/articles/41813668396435-Using-the-Blumira-API (public docs). - [Stellar Cyber](https://www.resultsiq.ai/docs/tools/stellar/): Uses: Alerts, incidents and log search. API docs: https://docs.stellarcyber.ai/Using/API/API-Intro.htm (public docs). - [RocketCyber](https://www.resultsiq.ai/docs/tools/rocketcyber/): Uses: Alerts and incidents. Needs: The API is read-only. API docs: https://api-doc.rocketcyber.com/ (public docs). - [N-able Adlumin](https://www.resultsiq.ai/docs/tools/adlumin/): Uses: Alerts. Needs: Requests are made per tenant. API docs: https://developer.n-able.com/adlumin/reference (public docs). - [Rapid7 InsightIDR](https://www.resultsiq.ai/docs/tools/insightidr/): Uses: Alerts, incidents and log search. API docs: https://docs.rapid7.com/insightidr/insightidr-rest-api/ (public docs). - [Splunk](https://www.resultsiq.ai/docs/tools/splunk/): Uses: Alerts and log search. Needs: Splunk Enterprise Security adds endpoints for findings, investigations and risk. API docs: https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/10.2 (public docs). - [Elastic Security](https://www.resultsiq.ai/docs/tools/elastic/): Uses: Alerts, incidents and log search. API docs: https://www.elastic.co/docs/api/doc/kibana (public docs). - [Sumo Logic](https://www.resultsiq.ai/docs/tools/sumo/): Uses: Alerts and log search. API docs: https://www.sumologic.com/help/docs/api/ (public docs). - [Exabeam](https://www.resultsiq.ai/docs/tools/exabeam/): Uses: Alerts, incidents and log search. API docs: https://developers.exabeam.com/exabeam/reference/ (public docs). - [LogRhythm](https://www.resultsiq.ai/docs/tools/logrhythm/): Uses: Alerts, incidents and log search. API docs: https://developers.exabeam.com/logrhythm-siem/docs (public docs). - [Fortinet FortiSIEM](https://www.resultsiq.ai/docs/tools/fortisiem/): Uses: Alerts and incidents. Needs: The guide for version 6.7 is public. Guides for 7.x need a Fortinet login. API docs: https://docs.fortinet.com/document/fortisiem/6.7.5/integration-api-guide (public docs). - [Coro](https://www.resultsiq.ai/docs/tools/coro/): Uses: Alerts. API docs: https://developers.coro.net/openapi/reference/overview (public docs). - [Wazuh](https://www.resultsiq.ai/docs/tools/wazuh/): Uses: Alerts and agent health. Needs: Open source. Alerts come through the Wazuh indexer’s API. API docs: https://documentation.wazuh.com/current/user-manual/api/reference.html (public docs). - [SaaS Alerts](https://www.resultsiq.ai/docs/tools/saasalerts/): Uses: Alerts. API docs: https://help.saasalerts.kaseya.com/help/Content/How-To/using-the-saas-alerts-api.htm (public docs). - [Field Effect MDR](https://www.resultsiq.ai/docs/tools/fieldeffect/): Uses: What the API covers isn’t public; its docs need a Field Effect login. Needs: An API key and an approved IP address, both from Field Effect support. API docs: https://support.fieldeffect.com/en/support/solutions/articles/16000205372 (docs need a login). Note: Field Effect’s API needs a key and an approved IP address from Field Effect support. ## Email security - [Avanan](https://www.resultsiq.ai/docs/tools/avanan/): Uses: Threats and remediation. Needs: A client ID and secret. MSPs use an MSP key, and Avanan support issues them if you don’t have one. API docs: https://sc1.checkpoint.com/documents/Avanan_API_Reference/Topics-HEC-Avanan-API-Reference-Guide/Overview/API-Overview.htm (public docs). - [Mimecast](https://www.resultsiq.ai/docs/tools/mimecast/): Uses: Threats, remediation and users. Needs: An API application registered in Mimecast, which you can set up yourself. API docs: https://developer.services.mimecast.com/api-overview (public docs). - [IRONSCALES](https://www.resultsiq.ai/docs/tools/ironscales/): Uses: Threats and remediation. Needs: A company token from Settings > General, exchanged for a scoped token. Limit: 120 calls a minute. API docs: https://appapi.ironscales.com/appapi/docs/ (public docs). - [Abnormal](https://www.resultsiq.ai/docs/tools/abnormal/): Uses: Threats and remediation. Needs: A token from the Abnormal portal, under Settings > Integrations > Abnormal REST API. API docs: https://api.swaggerhub.com/apis/abnormal-security/abx/1.8.0 (public docs). - [Proofpoint](https://www.resultsiq.ai/docs/tools/pfpt/): Uses: Threats. Needs: A service principal and secret from the TAP Dashboard settings. API docs: https://help.proofpoint.com/Threat_Insight_Dashboard/API_Documentation (public docs). - [Proofpoint Essentials](https://www.resultsiq.ai/docs/tools/pfpte/): Uses: Users. Needs: An organization admin’s credentials. The address depends on your Essentials stack (us1, eu1 and others). API docs: https://us1.proofpointessentials.com/api/v1/docs/index.php (public docs). - [Material Security](https://www.resultsiq.ai/docs/tools/material/): Uses: Threats and users. Needs: A token from Integrations > API and MCP > Tokens. The address is your own instance. API docs: https://docs.material.security/reference (public docs). - [Barracuda](https://www.resultsiq.ai/docs/tools/barracuda/): Uses: Account and email traffic numbers. The API is read-only for now. Needs: An app registered in the Barracuda Token Service. The API is in beta, for the US and UK regions. API docs: https://documentation.campus.barracuda.com/wiki/display/EGD/API+Overview (public docs). Note: Barracuda’s email API is an early, read-only version, so Control Center can read its account and traffic numbers only. - [SpamTitan](https://www.resultsiq.ai/docs/tools/spamtitan/): Uses: Threats. API docs: https://api-spamtitan.titanhq.com/ (public docs). - [EasyDMARC](https://www.resultsiq.ai/docs/tools/easydmarc/): Uses: Domains, DMARC reports and DNS checks. API docs: https://developers.easydmarc.com/ (public docs). ## Backup - [Datto BCDR](https://www.resultsiq.ai/docs/tools/dattobcdr/): Uses: Backup jobs and restore checks. Needs: A Datto Partner Portal admin creates the key under Admin > Integrations > API Keys. API docs: https://portal.dattobackup.com/integrations/api (docs need a login). - [Datto SaaS Protection](https://www.resultsiq.ai/docs/tools/dattosaas/): Uses: Backup jobs and which accounts are backed up. Needs: A Datto Partner Portal admin creates the key under Admin > Integrations > API Keys. API docs: https://portal.dattobackup.com/integrations/api (docs need a login). - [Veeam](https://www.resultsiq.ai/docs/tools/veeam/): Uses: Backup jobs and restore checks. Needs: For MSPs, Veeam Service Provider Console uses API keys created in its portal. API docs: https://helpcenter.veeam.com/references/vbr/13/rest/1.3-rev2/tag/SectionAbout (public docs). Service Provider Console: https://helpcenter.veeam.com/references/vac/9.3/rest/. - [Acronis](https://www.resultsiq.ai/docs/tools/acronis/): Uses: Backup jobs. Needs: An API client (ID and secret) registered in the management console. The address depends on your data center. API docs: https://developer.acronis.com/doc/account-management/v2/guide/getting-started/authenticating.html (public docs). - [Axcient x360Recover](https://www.resultsiq.ai/docs/tools/axcient/): Uses: Backup jobs and restore checks. Needs: An administrator creates an API key in the partner portal, under Settings > API Keys. API docs: https://developer.axcient.com/ (public docs). - [Cove Data Protection](https://www.resultsiq.ai/docs/tools/cove/): Uses: Backup jobs. API docs: https://documentation.n-able.com/covedataprotection/USERGUIDE/documentation/Content/service-management/json-api/home.htm (public docs). - [Rubrik](https://www.resultsiq.ai/docs/tools/rubrik/): Uses: Backup jobs and restore checks. Needs: A service account (client ID and secret). Tokens come from your tenant’s my.rubrik.com address. API docs: https://developer.rubrik.com/ (public docs). - [Dropsuite](https://www.resultsiq.ai/docs/tools/dropsuite/): Uses: Which accounts are backed up. Needs: API tokens are for direct partners and distributors of Dropsuite (NinjaOne SaaS Backup). API docs: https://help.dropsuite.com/hc/en-us/articles/20422080552855-15-API-Settings (partner access). - [Keepit](https://www.resultsiq.ai/docs/tools/keepit/): Uses: Backup jobs and which accounts are backed up. Needs: API token credentials created in Keepit. API docs: https://developers.keepit.com/authentication (public docs). - [AvePoint](https://www.resultsiq.ai/docs/tools/avepoint/): Uses: Backup jobs and which accounts are backed up. Needs: An app registered in AvePoint Online Services. Token addresses depend on your region. API docs: https://learn.avepoint.com/docs/Overview.html (public docs). - [Redstor](https://www.resultsiq.ai/docs/tools/redstor/): Uses: Backup jobs. Needs: A Partner Admin creates a service account. Redstor’s docs tie the API to its newer pricing plan. API docs: https://helpdesk.redstor.com/support/solutions/articles/4000219746-1607-how-to-use-the-redapi (public docs). ## Documentation - [IT Glue](https://www.resultsiq.ai/docs/tools/itglue/): Uses: Documentation, read and write and stored passwords. Needs: The Enterprise plan. An administrator creates the key under Admin > Settings, and North America, the EU and Australia have different addresses. API docs: https://api.itglue.com/developer/ (public docs). - [Hudu](https://www.resultsiq.ai/docs/tools/hudu/): Uses: Documentation, read and write and stored passwords. Needs: Admins create keys under Admin > API Keys. The full reference is inside your Hudu instance. API docs: https://support.hudu.com/hc/en-us/articles/11422780787735-REST-API (docs need a login). - [Confluence](https://www.resultsiq.ai/docs/tools/confluence/): Uses: Documentation, read and write. Needs: An Atlassian account email and API token, against your site address. API docs: https://developer.atlassian.com/cloud/confluence/rest/v2/ (public docs). - [SharePoint](https://www.resultsiq.ai/docs/tools/sharepoint/): Uses: Documentation, read and write. Needs: A Microsoft Entra app with Microsoft Graph permissions. Some permissions need admin consent. API docs: https://learn.microsoft.com/en-us/graph/api/resources/sharepoint?view=graph-rest-1.0 (public docs). - [Notion](https://www.resultsiq.ai/docs/tools/notion/): Uses: Documentation, read and write. Needs: An internal connection token, or OAuth. API docs: https://developers.notion.com/reference/intro (public docs). ## Microsoft 365 and identity - [Microsoft 365](https://www.resultsiq.ai/docs/tools/m365/): Uses: Users, MFA status, sign-ins and licenses. Needs: A Microsoft Entra app with Microsoft Graph permissions, and admin consent where required. API docs: https://learn.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0 (public docs). - [Google Workspace](https://www.resultsiq.ai/docs/tools/gws/): Uses: Users, MFA status, sign-ins and licenses. Needs: A Google Cloud project. A service account needs domain-wide delegation from a super admin. API docs: https://developers.google.com/workspace/admin/overview (public docs). - [Microsoft Entra ID](https://www.resultsiq.ai/docs/tools/entra/): Uses: Users, MFA status and sign-ins. Needs: Sign-in logs need Microsoft Entra ID P1 or P2, and AuditLog.Read.All or Directory.Read.All. API docs: https://learn.microsoft.com/en-us/graph/api/resources/identity-network-access-overview?view=graph-rest-1.0 (public docs). - [Okta](https://www.resultsiq.ai/docs/tools/okta/): Uses: Users, MFA status and sign-ins. Needs: A scoped OAuth 2.0 service app (Okta’s recommendation) or an API token. API docs: https://developer.okta.com/docs/api/openapi/okta-management/guides/overview (public docs). - [JumpCloud](https://www.resultsiq.ai/docs/tools/jumpcloud/): Uses: Users, MFA status and sign-ins. Needs: An admin API key. An admin with the Billing role has to turn on API access. API docs: https://docs.jumpcloud.com/ (public docs). - [Duo](https://www.resultsiq.ai/docs/tools/duo/): Uses: MFA status and sign-ins. Needs: An Owner creates an Admin API application. Duo Essentials, Advantage or Premier; each account has its own API hostname. API docs: https://duo.com/docs/adminapi (public docs). - [CIPP](https://www.resultsiq.ai/docs/tools/cipp/): Uses: MFA status and sign-ins. Needs: An API client set up in CIPP (Entra client credentials), against your own CIPP address. API docs: https://docs.cipp.app/api-documentation/setup-and-authentication (public docs). - [Microsoft Purview](https://www.resultsiq.ai/docs/tools/purview/): Uses: Audit log searches, eDiscovery, sensitivity labels and data loss prevention. Needs: Through Microsoft Graph, with a Microsoft Entra app. API docs: https://learn.microsoft.com/purview/developer/microsoft-purview-sdk-documentation-overview (public docs). ## Network - [Cisco Meraki](https://www.resultsiq.ai/docs/tools/meraki/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: An API key from Organization > API & Webhooks. API docs: https://developer.cisco.com/meraki/api-v1/getting-started/ (public docs). - [Ubiquiti UniFi](https://www.resultsiq.ai/docs/tools/unifi/): Uses: Device status and uptime and configuration and firmware. Needs: A Site Manager API key from unifi.ui.com, under Settings > API Keys. It’s read-only for now. API docs: https://developer.ui.com/site-manager/v1.0.0/gettingstarted (public docs). - [Fortinet FortiGate](https://www.resultsiq.ai/docs/tools/fortigate/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: The full REST reference is on the Fortinet Developer Network, which needs two Fortinet employees to sponsor your account. API docs: https://fndn.fortinet.net/ (partner access). - [SonicWall](https://www.resultsiq.ai/docs/tools/sonicwall/): Uses: Configuration and firmware. Needs: A full admin turns on API access in Device > Settings > Administration. API docs: https://sonicos-api.sonicwall.com (public docs). - [Auvik](https://www.resultsiq.ai/docs/tools/auvik/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: A per-user API key. The address depends on your region. API docs: https://support.auvik.com/hc/en-us/articles/360031007111-Auvik-API-Integration-Guide (public docs). - [Domotz](https://www.resultsiq.ai/docs/tools/domotz/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: An API key from Portal Settings > API Key. API docs: https://portal.domotz.com/developers/ (public docs). - [Liongard](https://www.resultsiq.ai/docs/tools/liongard/): Uses: Configuration and firmware and alerts. Needs: An access key ID and secret. The address is your own Liongard instance. API docs: https://docs.liongard.com/reference/developer-guide (public docs). - [PRTG](https://www.resultsiq.ai/docs/tools/prtg/): Uses: Device status and uptime and alerts. Needs: An API key from Account Settings > My Account > API Keys. API docs: https://www.paessler.com/support/prtg/api/v2/overview/index.html (public docs). - [Cisco Catalyst Center](https://www.resultsiq.ai/docs/tools/catalyst/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: Catalyst Center credentials, exchanged for a token that lasts 60 minutes. API docs: https://developer.cisco.com/docs/catalyst-center/getting-started/ (public docs). - [Aruba Central](https://www.resultsiq.ai/docs/tools/aruba/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: New Central uses a personal API client in HPE GreenLake. Classic Central uses an API Gateway token. API docs: https://developer.arubanetworks.com/new-central/docs/generating-and-managing-access-tokens (public docs). Classic Central: https://developer.arubanetworks.com/hpe-aruba-networking-central/docs/rest-api-getting-started. - [Ruckus](https://www.resultsiq.ai/docs/tools/ruckus/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: RUCKUS One has regional addresses. SmartZone has an API guide for each release. API docs: https://docs.ruckus.cloud/api (public docs). SmartZone: https://support.ruckuswireless.com/documents/6125-ruckus-smartzone-lt-ga-public-api-reference-guide-sz144-7-3-0. - [WatchGuard Cloud](https://www.resultsiq.ai/docs/tools/watchguard/): Uses: Configuration and firmware and alerts. API docs: https://www.watchguard.com/help/docs/API/Content/en-US/home.html (public docs). ## Billing and accounting - [QuickBooks Online](https://www.resultsiq.ai/docs/tools/qbo/): Uses: Invoices. Needs: An app on the Intuit Developer portal. Intuit’s free Builder tier caps some read calls. API docs: https://developer.intuit.com/app/developer/qbo/docs/get-started (public docs). - [Xero](https://www.resultsiq.ai/docs/tools/xero/): Uses: Invoices. Needs: An OAuth 2.0 app. Xero’s free Starter tier allows five connections, and paid tiers allow more. API docs: https://developer.xero.com/documentation/getting-started-guide/ (public docs). - [Stripe](https://www.resultsiq.ai/docs/tools/stripe/): Uses: Invoices. Needs: An API key from your Stripe account. API docs: https://docs.stripe.com/api (public docs). - [Sherweb](https://www.resultsiq.ai/docs/tools/sherweb/): Uses: Costs and usage. Needs: API keys from the Security > APIs section of the Sherweb partner portal. API docs: https://developers.sherweb.com/docs/get-started (partner access). - [QuoteWerks](https://www.resultsiq.ai/docs/tools/quotewerks/): Uses: Quotes. Needs: QuoteWerks Web; the desktop edition has no web API. The key is under Setup > Options > Zapier and API. API docs: https://qwwapi.quotewerks.com/docs (public docs). Note: QuoteWerks connects through its QuoteWerks Web API. The desktop edition has no web API. - [Sage Intacct](https://www.resultsiq.ai/docs/tools/intacct/): Uses: Accounting data, once Sage approves the connection. Needs: A Web Services license (sender ID) from Sage. The connection depends on Sage’s approval. API docs: https://developer.intacct.com/ (partner access). Note: Sage opens the Intacct API through its developer program, so this connection depends on Sage’s approval. - [Pax8](https://www.resultsiq.ai/docs/tools/pax8/): Uses: Costs and usage. Needs: API credentials from the Pax8 Integrations Hub, created by a Partner Admin. API docs: https://devx.pax8.com/docs/introduction (partner access). Note: Pax8 opens its API to its partners, so Control Center connects through your own Pax8 partner account. - [ConnectWise CPQ](https://www.resultsiq.ai/docs/tools/cwcpq/): Uses: Quotes, once ConnectWise approves the connection. Needs: The docs need a ConnectWise Developer Network account. ConnectWise opens the CPQ API to its program partners. API docs: https://developer.connectwise.com/Products/ConnectWise_CPQ (partner access). Note: ConnectWise opens the CPQ API to its own program partners, so this connection depends on ConnectWise. - [Gradient MSP](https://www.resultsiq.ai/docs/tools/gradient/): Uses: Billing data, once Gradient approves the connection. Needs: Vendors get an API key through Gradient’s Technology Alliances team, and each MSP adds its own partner key. API docs: https://api-docs.meetgradient.com/docs/getting-started (partner access). Note: Gradient connects outside platforms through its alliance program, so this connection depends on Gradient. - [Microsoft Partner Center](https://www.resultsiq.ai/docs/tools/partnercenter/): Uses: Costs and usage. Needs: For Microsoft CSP partners. API docs: https://learn.microsoft.com/en-us/partner-center/developer/partner-center-rest-api-reference (public docs). - [Ingram Micro Xvantage](https://www.resultsiq.ai/docs/tools/ingram/): Uses: Costs and usage. Needs: For Ingram Micro reseller accounts. API docs: https://developer.ingrammicro.com/reseller/getting-started (public docs). - [Quoter](https://www.resultsiq.ai/docs/tools/quoter/): Uses: Quotes. API docs: https://docs.quoter.com/ (public docs). ## Security training and compliance - [KnowBe4](https://www.resultsiq.ai/docs/tools/knowbe4/): Uses: Training completion and phishing tests. Needs: The reporting API comes with the Platinum, Diamond, SAT Foundation and SAT Advanced plans. The address depends on your region. API docs: https://developer.knowbe4.com/rest/reporting (public docs). Note: KnowBe4’s reporting API comes with its Platinum, Diamond, SAT Foundation and SAT Advanced plans. - [Huntress Security Awareness Training](https://www.resultsiq.ai/docs/tools/huntresssat/): Uses: Phishing tests. Needs: The same Huntress API key. Phishing campaign results are part of the Huntress API. API docs: https://api.huntress.io/docs (public docs). - [Vanta](https://www.resultsiq.ai/docs/tools/vanta/): Uses: Training completion and compliance controls. Needs: An admin creates an OAuth app in Settings > Developer Console. API docs: https://developer.vanta.com/ (public docs). - [Drata](https://www.resultsiq.ai/docs/tools/drata/): Uses: Compliance controls. Needs: An API key or OAuth. Some endpoints need specific plan features. API docs: https://developers.drata.com/ (public docs). ## Vulnerability scanning - [Tenable](https://www.resultsiq.ai/docs/tools/tenable/): Uses: Vulnerabilities, assets and scans. Needs: Includes an MSSP Portal API that works across clients. API docs: https://developer.tenable.com/reference (public docs). - [Qualys](https://www.resultsiq.ai/docs/tools/qualys/): Uses: Vulnerabilities, assets and scans. API docs: https://docs.qualys.com/en/vm/qweb-all-api/mergedProjects/qapi-user/get_started/get_started.htm (public docs). - [Rapid7 InsightVM](https://www.resultsiq.ai/docs/tools/insightvm/): Uses: Vulnerabilities, assets and scans. API docs: https://help.rapid7.com/insightvm/en-us/api/index.html (public docs). - [ConnectSecure](https://www.resultsiq.ai/docs/tools/connectsecure/): Uses: Vulnerabilities and assets. Needs: The API reference is inside the ConnectSecure portal, under your profile. API docs: https://cybercns.atlassian.net/wiki/spaces/CVB/pages/2128314664/API+FAQ (docs need a login). Note: ConnectSecure’s API reference is inside its portal, under your profile. - [runZero](https://www.resultsiq.ai/docs/tools/runzero/): Uses: Assets. API docs: https://help.runzero.com/docs/leveraging-the-api/ (public docs). ## DNS filtering - [DNSFilter](https://www.resultsiq.ai/docs/tools/dnsfilter/): Uses: Filtering policies and blocked threats. Needs: An API key from Account Settings in the dashboard. API docs: https://api.dnsfilter.com/docs (public docs). - [Cisco Umbrella](https://www.resultsiq.ai/docs/tools/umbrella/): Uses: Filtering policies, agent health and blocked threats. Needs: An Umbrella API key and secret, exchanged for an OAuth 2.0 token. API docs: https://developer.cisco.com/docs/cloud-security/umbrella-api-getting-started/ (public docs). - [Cloudflare Zero Trust](https://www.resultsiq.ai/docs/tools/cloudflare/): Uses: Filtering policies, agent health and blocked threats. Needs: A scoped API token with Zero Trust permissions. API docs: https://developers.cloudflare.com/cloudflare-one/api-terraform/ (public docs). - [Zscaler](https://www.resultsiq.ai/docs/tools/zscaler/): Uses: Filtering policies and agent health. Needs: API clients and roles in ZIdentity (Zscaler OneAPI). Zscaler now calls the older ZIA API legacy. API docs: https://help.zscaler.com/zia/getting-started-zia-api (public docs). - [SafeDNS](https://www.resultsiq.ai/docs/tools/safedns/): Uses: Filtering policies. Needs: Your SafeDNS account sign-in. The API is in beta. API docs: https://docs.safedns.com/books/rest-api/page/rest-api-guide (public docs). - [WebTitan](https://www.resultsiq.ai/docs/tools/webtitan/): Uses: Filtering policies and blocked threats. API docs: https://apidoc.webtitancloud.com/ (public docs). ## Passwords - [1Password](https://www.resultsiq.ai/docs/tools/1password/): Uses: Vault items and user provisioning. Needs: 1Password Business, with a token from the integration you set up, such as Events Reporting. API docs: https://www.1password.dev/events-api (public docs). - [Bitwarden](https://www.resultsiq.ai/docs/tools/bitwarden/): Uses: User provisioning. Needs: A Teams or Enterprise organization. The organization API key is in the Admin Console; US, EU and self-hosted addresses differ. API docs: https://bitwarden.com/help/public-api/ (public docs). - [Passportal](https://www.resultsiq.ai/docs/tools/passportal/): Uses: Vault items. Needs: An API key generated in Passportal. API docs: https://developer.n-able.com/passportal/docs/introduction (public docs). - [Devolutions](https://www.resultsiq.ai/docs/tools/devolutions/): Uses: Vault items and user provisioning. Needs: Devolutions Server: an application key and secret. The reference is built into your server. API docs: https://docs.devolutions.net/server/web-interface/utilities/api-documentation (public docs). - [Keeper Security](https://www.resultsiq.ai/docs/tools/keeper/): Uses: User provisioning. API docs: https://docs.keeper.io/enterprise-guide/keeper-msp/account-management-apis (public docs). ## Admin rights and allowlisting - [ThreatLocker](https://www.resultsiq.ai/docs/tools/threatlocker/): Uses: Approval requests. Needs: An API user (token or OAuth 2.0) created in the portal. The address is your own instance. API docs: https://threatlocker.kb.help/api-documentation/ (public docs). - [Admin By Request](https://www.resultsiq.ai/docs/tools/abr/): Uses: Approval requests. Needs: Included with your license. The API key is in Tenant Settings, and the address depends on your data center. API docs: https://docs.adminbyrequest.com/integrations/public-api.htm (public docs). ## Remote access - [ConnectWise ScreenConnect](https://www.resultsiq.ai/docs/tools/screenconnect/): Uses: Remote sessions. Needs: Install the RESTful API Manager extension. API docs: https://docs.connectwise.com/ConnectWise_ScreenConnect_Documentation/Supported_extensions/Administration/RESTful_API_Manager (public docs). Note: ScreenConnect connects through its RESTful API Manager extension. - [TeamViewer](https://www.resultsiq.ai/docs/tools/teamviewer/): Uses: Remote sessions and devices. API docs: https://webapi.teamviewer.com/api/v1/docs/index (public docs). - [Splashtop](https://www.resultsiq.ai/docs/tools/splashtop/): Uses: Remote sessions and devices. Needs: Splashtop’s Enterprise plans. API docs: https://support-splashtopbusiness.splashtop.com/hc/articles/16772899906459 (public docs). Note: Splashtop’s API comes with its Enterprise plans. - [BeyondTrust Remote Support](https://www.resultsiq.ai/docs/tools/beyondtrust/): Uses: Remote sessions. API docs: https://docs.beyondtrust.com/rs/reference (public docs). ## Teams, chat and phones - [Microsoft Teams](https://www.resultsiq.ai/docs/tools/teams/): Uses: Messages. Needs: A Microsoft Entra app with Microsoft Graph permissions. API docs: https://learn.microsoft.com/en-us/graph/api/resources/teams-api-overview (public docs). - [Slack](https://www.resultsiq.ai/docs/tools/slack/): Uses: Messages. Needs: A Slack app with a bot or user token. API docs: https://docs.slack.dev/apis/web-api/ (public docs). - [Zoom](https://www.resultsiq.ai/docs/tools/zoom/): Uses: Messages. Needs: An OAuth or Server-to-Server OAuth app with the scopes it needs. API docs: https://developers.zoom.us/docs/api/ (public docs). - [RingCentral](https://www.resultsiq.ai/docs/tools/ringcentral/): Uses: Messages. Needs: An app in the RingCentral Developer Console (client ID and secret). Some scopes need RingCentral’s approval. API docs: https://developers.ringcentral.com/api-reference (public docs). - [3CX](https://www.resultsiq.ai/docs/tools/3cx/): Uses: Users and call control. Needs: An 8SC+ license. The API client is created under Admin Console > Integrations > API. API docs: https://www.3cx.com/docs/configuration-rest-api/ (public docs). Note: 3CX’s API needs an 8SC+ license and covers users and call control. ## Cloud and files - [Microsoft Azure](https://www.resultsiq.ai/docs/tools/azure/): Uses: Costs and usage. Needs: A Microsoft Entra app with an Azure role on the subscriptions it reads. API docs: https://learn.microsoft.com/en-us/rest/api/azure/ (public docs). Cost Management: https://learn.microsoft.com/en-us/rest/api/cost-management/. - [AWS](https://www.resultsiq.ai/docs/tools/aws/): Uses: Costs and usage. Needs: AWS charges $0.01 for each Cost Explorer API request. API docs: https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/Welcome.html (public docs). - [Dropbox](https://www.resultsiq.ai/docs/tools/dropbox/): Uses: Users. API docs: https://www.dropbox.com/developers/documentation/http/documentation (public docs). - [Box](https://www.resultsiq.ai/docs/tools/box/): Uses: Users. Needs: An OAuth 2.0 access token. API docs: https://developer.box.com/reference (public docs). - [Wasabi](https://www.resultsiq.ai/docs/tools/wasabi/): Uses: Costs and usage. API docs: https://docs.wasabi.com/apidocs/api-guides (public docs). ## Reporting and lifecycle - [ScalePad](https://www.resultsiq.ai/docs/tools/scalepad/): Uses: Warranties. Needs: Lifecycle Manager’s API needs a higher subscription tier and an administrator’s API key. US only. API docs: https://developer.scalepad.com/ (public docs). - [Power BI](https://www.resultsiq.ai/docs/tools/powerbi/): Uses: Sending your metrics to dashboards. Needs: A Microsoft Entra app. A Power BI admin allows service principal access. API docs: https://learn.microsoft.com/en-us/rest/api/power-bi/ (public docs). - [Grafana](https://www.resultsiq.ai/docs/tools/grafana/): Uses: Sending your metrics to dashboards. Needs: A service account token. API docs: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/ (public docs). - [Datadog](https://www.resultsiq.ai/docs/tools/datadog/): Uses: Sending your metrics to dashboards. Needs: An API key, plus an application key for some endpoints. API docs: https://docs.datadoghq.com/api/latest/ (public docs). - [CloudRadial](https://www.resultsiq.ai/docs/tools/cloudradial/): Uses: Companies, users, endpoints, assessments and the service catalog. API docs: https://support.cloudradial.com/hc/en-us/articles/360050153571-Using-the-CloudRadial-API (public docs). - [Crewhu](https://www.resultsiq.ai/docs/tools/crewhu/): Uses: Surveys, users and contest metrics. API docs: https://get-help-tnt.crewhu.com/hc/en-us/articles/360002286094 (public docs). ## Automation platforms - [Rewst](https://www.resultsiq.ai/docs/tools/rewst/): Uses: Starting your workflows. Needs: Rewst’s API is GraphQL, and Rewst workflows can also start from webhook triggers. API docs: https://docs.rewst.help/documentation/automations/actions-in-rewst/generic-graphql-request-action (public docs). - [Power Automate](https://www.resultsiq.ai/docs/tools/powerautomate/): Uses: Starting your workflows. Needs: Through the Dataverse Web API, for flows that live in solutions. API docs: https://learn.microsoft.com/en-us/power-automate/manage-flows-with-code (public docs). - [n8n](https://www.resultsiq.ai/docs/tools/n8n/): Uses: Starting your workflows. Needs: Not on the free trial: n8n Cloud Starter, Pro or Enterprise, or any self-hosted edition. API docs: https://docs.n8n.io/connect/n8n-api (public docs). - [Zapier](https://www.resultsiq.ai/docs/tools/zapier/): Uses: Starting your workflows. Needs: Zapier’s Workflow API needs a publicly listed Zapier integration or White Label onboarding. API docs: https://docs.zapier.com/powered-by-zapier/zap-creation/getting-started (partner access). - [Make](https://www.resultsiq.ai/docs/tools/make/): Uses: Starting your workflows. Needs: Use your organization’s zone address, such as eu1 or us1. API docs: https://developers.make.com/api-documentation (public docs). ## No public API yet We couldn’t find a public API for these tools, so Control Center can’t connect to them yet. If your vendor gives you API docs for one of them, send them to us and we’ll check them. - Todyl (Endpoint security) - ConnectWise SIEM (SIEM and managed SOC) - Barracuda XDR (SIEM and managed SOC) - IT Portal (SI Portal) (Documentation) - ITBoost (Documentation) - Breach Secure Now (Security training and compliance) - Hook Security (Security training and compliance) - Apptega (Security training and compliance) - Compliance Scorecard (Security training and compliance) - Cynomi (Security training and compliance) - RapidFire VulScan (Vulnerability scanning) - RapidFire Network Detective (Vulnerability scanning) - RapidFire Cyber Hawk (Vulnerability scanning) - Nodeware (Vulnerability scanning) - AutoElevate (Admin rights and allowlisting) - BrightGauge (Reporting and lifecycle) - SmileBack (Reporting and lifecycle) ## Not listed? If it has a documented API, Control Center can connect to it. Email connor.reece@resultsiq.ai with the tool’s name and a link to its API docs. --- ## Contact - connor.reece@resultsiq.ai