RMM & Endpoint

Auvik

Browse your Auvik network inventory and alerts in plain language - devices, networks, interfaces, configs, and alert history per tenant.

Dex connects to the Auvik API v1 so admins can run network monitoring conversationally - inventory devices, networks, and interfaces, review saved device configurations, and triage alert history for a tenant. Dex can also dismiss an alert with approval when NOC state needs clearing. Auvik is an MSP global app: one shared Basic-auth user and API key covers the whole partner, and each Dex tenant is confined to its own Auvik tenant (client or multi-client) by the tenant_id identifier. The MSP master connection lists the tenant roster; scoped children force the tenants filter on every inventory and alert read.

Start free →See Dex Live

What Dex does with Auvik

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

Inventory Auvik devices, networks, and interfaces for a tenant - filter by device type, online status, or network type
Read a single device, network, or interface (ownership-checked on a scoped child)
Review saved device configurations captured by Auvik
Triage alert history for a tenant - filter by open or closed status
Dismiss an alert when NOC state needs clearing - with approval
Read this tenant's Auvik tenant detail
List the full tenant roster from the MSP master connection
Deploy as an MSP global app - one shared API user and key, each customer confined to its Auvik tenant by tenant_id

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>List the switches Auvik has discovered for this tenant
>Show me the open alerts in Auvik right now
>Which devices are offline according to Auvik?
>Pull the saved configuration for the core router
>Dismiss Auvik alert 12345678901 - it was a false positive

Policy actions

Every action Dex can take on Auvik is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`auvik_list_devices`	List Auvik devices for this tenant	—
`auvik_get_device`	Read an Auvik device (ownership-checked on a scoped child)	—
`auvik_list_networks`	List Auvik networks for this tenant	—
`auvik_get_network`	Read an Auvik network (ownership-checked on a scoped child)	—
`auvik_list_interfaces`	List Auvik interfaces for this tenant	—
`auvik_get_interface`	Read an Auvik interface (ownership-checked on a scoped child)	—
`auvik_list_configurations`	List Auvik device configurations for this tenant	—
`auvik_get_configuration`	Read an Auvik configuration (ownership-checked on a scoped child)	—
`auvik_list_alerts`	List Auvik alert history for this tenant	—
`auvik_get_alert`	Read an Auvik alert (ownership-checked on a scoped child)	—
`auvik_dismiss_alert`	Dismiss an Auvik alert (ownership-checked on a scoped child)	approval
`auvik_get_tenant`	Read this Auvik tenant detail	—
`auvik_list_tenants`	List every Auvik tenant (master connection only)	—

How to configure Auvik

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In Auvik, go to Admin > Users and create or pick a service account with API Access.
2
From that user menu, generate an API Key (shown once) for Dex.
3
Note your cluster code from the dashboard URL - the segment between auvikapi. and .my.auvik.com (e.g. us1, eu1, ca1).
4
In Dex, enable the Auvik integration and paste the login email, API key, and region. Leave tenant_id blank on the MSP master connection.
5
Dex validates the credentials with a live call, then discovery maps each Dex tenant to its Auvik tenant_id from GET /v1/tenants on the master.

Credentials required

api_username: Auvik login email of a service account with API Access
api_key: API key generated for that Auvik user (shown once)
api_region: Cluster code from your dashboard URL (us1-us4, eu1, eu2, ca1, au1, lnx). Default us1
tenant_id: This tenant's Auvik tenant id (numeric snowflake string). Leave blank on the MSP master connection

Requirements

•An Auvik subscription with an API user that has API Access
•The cluster code matching your Auvik dashboard region (a wrong region answers HTTP 308 with the correct cluster)
•Read-focused: Dex browses inventory and alerts and can dismiss alerts, but does not modify device settings
•For MSPs, deploy as a global app - one shared credential, each Dex tenant scoped to its Auvik tenant_id