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 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
  • Generate and delete hotspot vouchers; authorize or revoke guest access for a client
  • Read and change networks/VLANs, SSIDs, WANs, VPNs, DNS policies, firewall policies and ACL rules

​
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 and deleting vouchers runs autonomously; client actions such as authorizing a guest require technician approval. Everything else Read Only.
Every writable group at Read/Write. Device, client and voucher writes run autonomously; firewall and network changes (allow rules, port forwards, VPNs) require technician approval.
Every writable group at Read/Write with no approval. Only a write that sets a WiFi passphrase or another secret still asks a technician.

​
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

On the agent’s Tools & Settings tab, click Networking and expand the Ubiquiti UniFi block. Pick one of its Presets, which are the access profiles above, or set each permission group yourself.
3

Set approval requirements

Turn on Require approval for each group whose writes a technician should sign off. The access profiles set a starting point.
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.