Skip to main content
The UniFi API tool gives Neo agents direct access to your UniFi network — pull a site’s gateway, switch and AP status into the ticket, find the client behind a connectivity complaint, issue a guest voucher, and, with your approval, restart the access point that stopped responding. Which API it calls follows the connection type you chose when you connected UniFi: The permission groups, the approval rules and the agent setup below are the same for all three. A path that belongs to another connection type is refused with a message naming the one that applies, so an agent corrects itself instead of retrying.
Automatically enabled when you configure UniFi permissions in your agent workflow. No manual toggle needed.
Agents load the UniFi API skill first, which carries the endpoint tables for each connection type, pagination and filter syntax, and the pacing rule that matters most on Site Manager: the Connector allows 100 requests per minute per console.

​
What It Does

  • List the consoles and sites the connected account manages, and every device across the fleet with its online state
  • Read ISP latency, packet-loss, throughput and uptime per site
  • Read a site’s adopted devices with live statistics, and the clients connected to them
  • Restart a device or power-cycle a PoE port (always behind technician approval)
  • Generate hotspot vouchers; authorize or revoke guest access for a client and delete vouchers (always behind technician approval)
  • Read and change networks/VLANs, SSIDs, WANs, VPNs, DNS policies, firewall policies and ACL rules (writes always behind technician approval)

​
Permission Groups

Each group has an access level: Disabled, Read Only, or Read/Write (Consoles & Sites only ever offers Read Only).

​
Access Profiles

All groups Read Only. The agent can look up any resource but never changes anything.
Hotspot Vouchers and Clients at Read/Write — issuing a voucher runs autonomously; authorizing a guest still requires technician approval on every call. Everything else Read Only.
Every writable group at Read/Write, but every write requires technician approval — not just the mandatorily-forced ones.
Issuing vouchers runs autonomously. Device actions, network/firewall changes, guest authorization and voucher deletion still always require technician approval — that override is never optional.

​
Safety Controls

​
How to Configure

1

Connect UniFi

In the Neo Dashboard, open the Networking integrations category, pick your Connection type and enter its credentials — a Site Manager API key, a console API key with its URL, or a controller URL with a local admin’s username and password. See Connecting UniFi to Neo for which one your controller needs.
2

Configure permissions

In your agent workflow’s Integrations tab, choose an access profile or customize each permission group.
3

Set approval requirements

Every write except issuing a hotspot voucher already requires technician approval; decide whether voucher issue should too.
Start with Read Only — most network tickets are answered by reading the gateway’s WAN status, the AP’s client count and the client’s signal, with no write at all.