Auvik: network device inventory and alert counts per site

Auvik knows your customers' networks — every switch, router, firewall and access point, whether it's online, and what's alerting right now. Current reads that estate and turns it into a value signal: how many devices you monitor for each customer, the make-up of their network, and how many alerts are open by severity. It's the picture a CIO wants in a business review, assembled for you instead of screenshotted by hand.

The connection is read-only in the strictest sense. Current only ever reads from Auvik and never writes back — the single write the Auvik API exposes (dismissing an alert) is not wired into Current at all, so nothing you do here can change an Auvik record.

Auvik authenticates with HTTP Basic auth: your API username is an Auvik user's login (email), and the password is an API key generated for that user. Best practice is a dedicated service-account user rather than a person, so the key survives staff turnover.

1. 1
   Create (or pick) a service-account user in Auvik

   In the Auvik dashboard, add a user Current will read as — for example integrations@yourmsp.com. Give it the role permissions it needs and authorize it for each client (Auvik tenant) you want Current to read. A key stops working the moment its owning user is deactivated, which is why a service account beats a person's login.
2. 2
   Generate an API key

   In the Auvik dashboard, follow "How to generate an API key" for that user and copy the key. Auvik shows it so you can copy it — store it safely; you paste it into Current once.
3. 3
   Note your region / cluster

   Look at your Auvik dashboard's address bar: the host is auvikapi.<region>.my.auvik.com-style, and the region is a short code like us1, us2, or eu1. You'll enter that code, not a full URL.
4. 4
   Paste it into Current

   In the left sidebar open Integrations (under Admin — Tenant Admins only), find the Auvik card, press Manage, and enter the Region/cluster, API Username, and API Key. Press Test connection: Current makes one cheap read against Auvik to prove the credentials before storing anything. The key is kept server-side and never shown back to the browser.

After you connect, Current lists your Auvik tenants (your customers and sites), then for each one pulls its device inventory and its open-alert counts. It refreshes on its own every 6 hours; the card shows the last sync time and live counts.

Every request Current makes to Auvik is a read (an HTTP GET), and only three read paths are allowed: the tenant list, device inventory, and alert history. Auvik's one write — dismissing an alert — is not in Current's allowlist and cannot be reached, even by a code path that tried. Current is a mirror of Auvik, never a control channel.

Auvik's tenant list and your Current company book are two directories, so Current matches them. On each sync it auto-links an Auvik tenant to a Current company when their names match exactly once after normalizing (lower-cased, with Inc/LLC/Ltd and punctuation stripped). Anything it can't match confidently is left for you.

• ＋Auto-matching never overrides a mapping you made by hand, and never guesses when a normalized name matches two companies — those are left unmapped for you to resolve.
• ＋Use the company-mapping panel on the Auvik card to link the leftovers: pick the right Current company for each unmatched Auvik tenant.
• ＋Unmapped Auvik tenants still sync — their devices and summary are stored — they just don't surface on a company record until they're mapped.

• ＋Auvik allows 2,500 requests per 5 minutes per IP. Current paces every request well under that and scopes each call to a single Auvik tenant, so a sync never brownouts your Auvik account. If Auvik asks it to slow down (a 429 with Retry-After), Current backs off and resumes.
• ＋If your account is on the wrong or a migrated region, Auvik answers with a 308 redirect to the right cluster. Current detects that, follows it, and remembers the resolved region on the connection — so a cluster migration doesn't break the sync.
• ＋Current never auto-retries a 400/401/403/404 from Auvik — those are configuration or permission problems (bad region, bad key, a client the API user isn't authorized for), surfaced on the card so you can fix them.