Build on the UniFi API.

Integrations, automations and custom tools on Ubiquiti’s official APIs: Network, Protect and Site Manager. Built by the engineers who run the networks.

Talk to an Engineer

noc@unifiedit — zshapi.ui.com

{
  "data": [
    {
      "id": "900A6F00…:123456789",
      "type": "console",
      "ipAddress": "203.0.113.10",
      "reportedState": {
        "hostname": "UDM-Pro-HQ",
        "state": "connected",
        "version": "4.1.13"
      }
    },
    {
      "id": "900A6F00…:987654321",
      "type": "console",
      "ipAddress": "198.51.100.42",
      "reportedState": {
        "hostname": "UCG-Fiber-Plant-2",
        "state": "connected",
        "version": "4.1.13"
      }
    }
  ],
  "httpStatusCode": 200
}

Three official APIs, and we build on all of them

Ubiquiti publishes a local API on every console and a cloud API over every account. Which one a project uses depends on where the data lives and who needs to reach it.

Network API

Local

https://{console}/proxy/network/integration/v1

Runs on the gateway. Sites, devices, clients, Wi-Fi, firewall policies, hotspot and vouchers, with read and write access and an API key from the console.

Devices
Clients
Wi-Fi
Firewall
Hotspot
Vouchers
Port actions

Protect API

Local

https://{console}/proxy/protect/integration/v1

Cameras, NVRs, sensors and doorbells. Snapshots, live streams and a WebSocket of events for everything Protect sees.

Cameras
Snapshots
Events
Live streams
Sensors
Webhooks

Site Manager API

Cloud

https://api.ui.com/v1

One key over every console on the account. Hosts, sites, devices, ISP metrics and SD-WAN status, plus a connector proxy into any local console.

Hosts
Sites
Devices
ISP metrics
SD-WAN
Connector proxy

What the API can do

Ten things we have built or scripted for clients, with the exact call behind each one. Pick one on the left.

Site Manager API · Cloud

Network API · Local

Protect API · Local

Site Manager API · CloudGET/v1/hosts

Inventory every console you manage

One call returns every UniFi OS console on the account: model, firmware, IP, uptime and reachability. The starting point for fleet reporting across all of your clients.

curl -s https://api.ui.com/v1/hosts \
  -H "X-API-Key: $UI_API_KEY" -H "Accept: application/json"

Response

{
  "data": [{
    "id": "900A6F00…:123456789",
    "hardwareId": "e4f1…",
    "type": "console",
    "ipAddress": "203.0.113.10",
    "reportedState": { "hostname": "UDM-Pro-HQ", "state": "connected", "version": "4.1.13" }
  }],
  "httpStatusCode": 200,
  "nextToken": null
}

Keys are generated in Site Manager (Settings API Keys) or on the console (Network Control Plane Integrations). The Site Manager API’s own endpoints are read-only; writes go to the local Network and Protect APIs, directly or through the connector proxy.

What we build

Most projects are one of four shapes. All of them ship with source, documentation and a runbook for your team.

Custom dashboards

Client-facing or internal visibility: uptime, ISP health, device status and alerts, on your domain, with your branding.

Automated workflows

Event-driven runbooks: a port power-cycles when a camera drops, a ticket opens when a WAN degrades, a report lands every Monday.

Third-party integrations

UniFi talking to your PSA, ticketing, identity or access control: ConnectWise, Autotask, Jira, Entra, badge systems.

Multi-site tooling

Bulk configuration, fleet reporting and portfolio-wide health for MSPs and enterprises with dozens or hundreds of sites.

How a project runs

01
Scope
A thirty-minute call and a one-page scope: what triggers it, what it touches, what done looks like.
02
Build
Against the official APIs, in our lab, on your test site, with no reverse-engineered endpoints.
03
Deploy
In your environment or ours. Keys scoped to the minimum, secrets in your vault, logs you can read.
04
Support
Covered under the TAC, or handed over with source and a runbook, whichever you choose.

Scope a UniFi integration.

Tell us what you’re trying to automate, and we’ll scope it.