Skip to main content

Connect Auvik Network Management to Lexful

Set up Auvik credentials and the correct region, enable early-access syncing, and troubleshoot missing inventory.

Import your Auvik Network Management customers, sites, and network devices into Lexful.
​

Early access: This integration is still being tested, and imported data may be incomplete. You can enable syncing during setup or save your credentials and start later.
​

Before you begin

You need permission to manage integrations in your Lexful account and the following Auvik Network Management details:

  • Regional API URL: The HTTPS API address for the region hosting your Auvik account. For example, an account in us1 uses https://auvikapi.us1.my.auvik.com.

  • Auvik username: The username of the user who owns the API key.

  • API key: The key generated for that user. The connector pairs the username with this key.

Create a dedicated Auvik user for Lexful: In Auvik, create a new user with the API Access role only, and assign that user to the customers that Lexful should access. Lexful can import only the customers assigned to this user.

Use an Auvik user with tenant and inventory read access to every customer and site you want to import. A dedicated integration user makes access easier to maintain.

This connector uses Auvik Network Management credentials. Confirm that your Auvik subscription and user role permit the required API access.
​

Prepare your Auvik API key and region

  1. Sign in to Auvik as the user whose access Lexful should use.

  2. Open that user’s profile from the username menu and generate an API key. Store the key securely. If the option is unavailable, ask your Auvik administrator to check your role.

  3. Check the region in your Auvik dashboard address. In an address ending with .us1.my.auvik.com, the region is us1.

  4. Use the matching API origin: https://auvikapi.REGION.my.auvik.com. Enter only the origin, without an API endpoint path.

  5. Ask your administrator to confirm the key’s user can read the required tenants, sites, and device inventory.

For details, see Auvik’s API key guide and API integration guide.

Generating a replacement key invalidates the previous key. Update any other integrations using that key when you rotate it.
​

Connect Auvik

  1. In Lexful, switch to the account that should receive the imported data.

  2. Open Platform → Integrations → Sources.

  3. Find Auvik Network Management and select Set up early access.

  4. Enter the Regional API URL, Auvik username, and API key.

  5. Select Test Connection. After a successful test, Lexful displays Connection verified. You can save these credentials.

  6. To start syncing, select Enable early-access syncing when available. The checkbox starts unchecked. Read the early-access notice before selecting it.

  7. Follow the setup prompts to select objects and complete any required client-mapping review. Approve collection when ready.

When syncing is available and credentials pass verification, saving with the checkbox selected enables the connection. Lexful reports Early-access syncing enabled. Saving with the checkbox unchecked stores the connection without starting sync.
​

Start a connection you saved earlier

  1. Return to Sources and open your Auvik connection.

  2. If it shows Ready to start syncing, select Start syncing. Lexful verifies the saved credentials before enabling the connection.

  3. Once active, use Sync activity to review sync history and errors. Use Objects to review the configured object selection.
    ​

What to expect

The integration imports customers, sites, and devices visible to the Auvik user. Available device details can include native identifiers, customer and site relationships, IP and MAC addresses, online status, and firmware or software versions.
​

MSP containers organize the Auvik hierarchy and may not appear as separate customers or sites in Lexful. The import follows the customer and site ownership in Auvik.
​

A successful connection test checks tenant access. Review the first completed import to confirm device inventory and all expected sites are present. Import time depends on inventory size and Auvik’s API limits.
​

Troubleshooting

  • The connection test fails: Confirm the username matches the API key’s owner and the key is current. Check the regional API URL and user’s tenant permissions.

  • The URL redirects or the region changed: Enter the current regional API origin directly. Lexful requires HTTPS and does not follow Auvik API redirects.

  • The test passes, but devices or sites are missing: Ask your Auvik administrator to check the user’s site assignments, inventory permissions, and subscription access. A tenant test does not verify every device endpoint.

  • The connection is saved but nothing syncs: Open it and select Start syncing if available. Saving credentials without opting in does not start an import.

  • The key or user’s access changed: Open Connection to update credentials. Leave unchanged secrets blank, test the candidate values, then choose Save credentials. Connections awaiting activation may use the credential drawer.

If you need help, share the connection name, error text, and approximate failure time with Lexful Support. Omit API keys and other credentials from messages and screenshots.
​

Disconnect

Open the connection, select its three-dot menu, and choose Disconnect. Disconnecting removes the saved Lexful connection credentials; it does not revoke the API key in Auvik.

Did this answer your question?