Connect Domotz
Domotz is a network monitoring platform for MSPs and AV/IT integrators. A Collector — an on-site agent you run as an appliance, a VM, or a software install — discovers every device on a customer…
Written By Christopher Scaminaci
Last updated 6 days ago
Domotz is a network monitoring platform for MSPs and AV/IT integrators. A Collector — an on-site agent you run as an appliance, a VM, or a software install — discovers every device on a customer network and watches it continuously: whether it is up, how fast it responds, what its SNMP and TCP sensors report, how the network is wired together, and which PDU outlet each device is plugged into. Connecting Domotz to StackJack lets your AI assistant read all of that and act on it.
Connecting Domotz gives your AI a broad set of domotz_ MCP tools — MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:
- Inventory your Collectors and every device behind them, including installed applications, SNMP details, and detected device types
- Investigate uptime, response-time (round-trip delay) history, status-change history, internet speed-test results, and per-device monitored variables
- Triage alerts — list them over a time window, filter by severity or status, and resolve them
- Manage alert rules end to end (create, update, delete) and bind them to Collectors, devices, and contact channels
- Configure monitoring — sensors (Domotz calls them Eyes), IP-scan and network-interface policies, DHCP discovery, routed networks, and external hosts
- Control power — read a device's available power actions and its PDU outlets, then power on, off, cycle, or software-reboot
- Back up device configurations and read the backup history
- Open remote access — create a VPN session to a customer network, connect to a specific device, and take a snapshot from an ONVIF camera
- Organize with custom tags, inventory fields, teams and areas, and manage who has access to your Domotz account
How StackJack authenticates to Domotz
Domotz uses a static API key sent on every request. You create the key in the Domotz Portal and paste it into StackJack. There is no OAuth and no refresh flow. Domotz's public setup guide does not publish an automatic lifetime for these keys, so treat the key as a long-lived credential, rotate it on your own schedule, and revoke it in Domotz when it is no longer needed.
Your API base URL matters as much as the key
This is the one thing to get right. Domotz hosts accounts on regional cells, and the cell name is part of the hostname:
The cell is not something you can work out from your region alone — the number at the end is an index, and Domotz adds cells as it grows. Domotz shows the exact URL for your account on the same page as the API key, so copy both from that one screen. A perfectly valid key sent to the wrong cell will not authenticate.
Before you begin
- In StackJack: you need a role that can manage connectors (tenant Owner, a co-owner, or an Administrator).
- In Domotz: you need an account that can open Settings → API Key, plus that account's password to unlock key creation.
- Both values to hand: the API key and the API base URL shown next to it.
Step 1 — Create an API key in Domotz
- Sign in to the Domotz Portal with an account that can manage API keys.
- Go to Settings → API Key.
- Choose Full Access API Key. Do not choose Agent Activation: that key type can enroll Collectors but cannot read or manage Public API resources.
- Choose Create API Key, enter your account password to unlock key creation, and give the key a descriptive name (for example, "StackJack Integration").
- Copy the key immediately and store it securely — Domotz does not show it again after you close the popup.
- In the same popup, note the Endpoint shown for your account. This is the API base URL you need in the next step.
Step 2 — Add the credentials in StackJack
- In the StackJack portal, open Connectors.
- Find the Domotz card. Click How To Connect for these steps inline, or Configure to enter the credentials.
- Paste your Domotz API base URL (it must start with
https://and include the/public-api/v1path). - Paste your API key.
- Click Save.
What happens when you save
- The API key is stored encrypted in Azure Key Vault — never in the StackJack database, and never shown back to you.
- If this is the first time you configure Domotz, a Free-tier subscription for the connector is created automatically so its Free tools work right away.
- StackJack immediately live-validates the credentials by reading your Domotz account details. Validation never blocks the save: you will either see a success confirmation or a "saved but validation failed" warning with the reason.
- The connector card shows the current connection and validity status from then on.
The validation read is the cheapest authenticated account call StackJack uses and every Full Access key can make it, so a success here proves both that your key is good and that your API base URL points at the right cell. That is exactly the pair of things worth confirming before your AI starts working.
Plans and available tools
- Free includes Collector and device inventory, applications and device types, alerts and alert rules, alert-profile bindings, uptime and response-time history, speed-test results, monitored variables and datapoints, sensors, network-configuration policies, power-action and outlet listings, drivers and their execution logs, inventory fields, configuration-backup history, VPN session listings, network topology, access management, and your account's API usage and limits.
- Pro adds actions for alert rules and profile bindings, device and credential changes, sensor lifecycle, network-configuration policies, power and outlet control, drivers, custom tags and inventory fields, configuration backups, remote connections and VPN sessions, camera snapshots, and access management.
- Business offers the same tools as Pro with a higher usage allowance.
See the generated Domotz tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.
Domotz has no per-user sign-in for its API, so all AI traffic authenticates as the single API key — there is no per-user attribution. Current pricing and quotas are shown in the portal's Billing page and at checkout.
Two things to know about the tiers
Taking a camera snapshot is a read, but it is a Pro tool. It is the one exception to "reads are Free". Fetching a snapshot opens a real connection into the customer network — the same metered remote-connection budget a VPN session draws from — and returns an image of the customer's premises. Both of those make it worth putting behind the paid tier even though it changes nothing.
Know which actions are disruptive before you grant them. StackJack marks these as destructive: deletes (Collectors, devices, sensors, tags, users, alert rules, inventory fields), power and PDU outlet actions, custom-driver execution on a device, and bulk device-profile application. A few of these read more alarmingly than they behave — hiding a device and removing a device exclusion both use a delete operation in Domotz but neither destroys data — so each tool's description spells out what it actually does. Whether your AI application asks you to confirm before running one depends on that application's own settings — see Destructive tools and confirmation. Review those settings, and grant only the actions you want an AI to take.
Rate limits
Domotz enforces two limits: a maximum number of calls per minute and a maximum per rolling 24 hours. The actual ceilings depend on your Domotz plan, and Domotz does not publish default numbers.
StackJack paces requests conservatively per organization and backs off automatically if Domotz pushes back, so a long inventory read is usually just slower. Pacing is not a guarantee: retries are bounded, so a wide enough read can still come back throttled or time out. Narrow the read, honour any retry delay the vendor sends, and check whether a write landed before repeating it — see Retrying a failed or timed-out write.
Because the daily allowance is the one you can genuinely exhaust, the Get API Usage And Limits tool is available on every tier. Ask your AI to check it and you will see your account's real per-minute and per-day ceilings, how much of the daily allowance is already spent, and a breakdown by API key, source IP, and resource. That is the first thing to look at if calls start slowing down or failing.
Rotating or replacing the credentials
The API key is the recovery secret. If you regenerate or revoke it in Domotz, the stored credential becomes invalid. To restore access, open Connectors → Domotz → Configure in StackJack, paste the new key, and Save.
If you only need to correct the API base URL, you can leave the API key field blank and save — StackJack keeps the key it already has. This is the quickest fix for the most common Domotz setup mistake.
What the Domotz public API does not expose
Worth knowing up front, so you do not go looking for tools that cannot exist:
- Alert profiles and webhooks are configured in the Domotz Portal, not the API. StackJack can list your Shared Alert Profiles and bind them to Collectors and devices, but it cannot create or edit a profile. The newer alert rules are fully API-managed, so use those when you want your AI to build alerting itself.
- You cannot create a Collector through the API. Collectors are enrolled on-site.
- Teams, areas, and moving a Collector between teams require the Domotz Enterprise plan. Those tools return an error on other plans.
- One older tool is deprecated by Domotz — listing alert profiles for a specific user. Its replacement is included, and the deprecated tool's description says so.
Troubleshooting
Domotz tools
domotz_ · 159 tools · Free 80 · Pro 79
Account & Metadata
Collectors
Devices
Alerts & Alert Rules
Alert Profiles
Access Management
Custom Tags
Metrics & Datapoints
Sensors (Eyes)
Network Configuration
Power Management
Custom Drivers
Inventory Fields
Configuration Backups
Remote Connections & Multimedia
More in Connector guides
Connect Acronis Cyber Protect CloudConnect Action1Connect AddigyConnect AlertOpsStill need help? Ask the team