Aravolta + NetBox.
Automatic push sync against the NetBox REST API. Aravolta captures changes to your datacenters, rooms, zones, cabinets, tenants, assets, providers, patch panel ports, and cross connects, then mirrors them into NetBox in dependency order so every reference resolves.
{
"id": 17,
"name": "NLAMS01-PDU-1",
"site": { "name": "Amsterdam" },
"rack": { "name": "NLAMS01-RK-01" },
"serial": "5A2204E01123",
"custom_fields": {
"aravolta_asset_id": "112095"
}
}Automatic Push Sync
Changes are captured as they happen and reflected into NetBox by a background worker. No manual export, no nightly batch, no stale import. Pause it any time and queued changes resume when you turn it back on.
The Whole Topology, Not Just Devices
Datacenters, rooms, zones, cabinets, tenants, assets, internet providers, patch panel ports, and cross connects each map to their NetBox counterpart and are pushed in dependency order so references always resolve.
Automatic Traceability
Every synced object is stamped with its Aravolta id custom field (aravolta_asset_id on devices, aravolta_id on everything else), so the cross reference lives in NetBox itself, visible to every team and tool.
How the Integration Works
Aravolta talks to the NetBox REST API. No agents on the NetBox side and no database access, just an API token with the permissions you grant it.
Token-Based Authentication
A NetBox API token, stored encrypted (AES-256-GCM) and never displayed again. Validated automatically, so expired tokens surface a clear re-key prompt instead of silent failures.
Change Capture
When you create, edit, or delete an entity in Aravolta, the change is captured into a durable queue. Only fields that matter to NetBox trigger a sync, so routine monitoring writes never create noise.
Dependency-Ordered Sync
A background worker drains the queue in order: sites and tenants, then locations and racks, then devices, then providers, ports, and cables. Supporting objects like manufacturers, device types, roles, and primary IPs are resolved or created on demand.
Run History and Deletion Control
Every pass is recorded with what synced, what changed, and what failed, down to the NetBox validation message. Deleting an Aravolta entity can remove its NetBox counterpart too, configurable per entity type.
Getting Started in Three Steps
From zero to a fully mirrored topology in minutes. No NetBox-side installation.
Create a NetBox API Token
In NetBox, navigate to the API tokens page under your user profile. NetBox auto-generates the token value, so scope its permissions to what Aravolta should manage.
Connect in Aravolta
Go to Settings, Integrations, then NetBox. Paste your instance URL and token, save, and Aravolta verifies the connection immediately. Both legacy and v2 (nbt_) tokens are supported.
Enable Push Sync
Turn push sync on and run Push all once to mirror your current topology. From then on, every change flows automatically, and the entity dialogs show what is linked in NetBox.
No NetBox instance handy? The integration ships with a built-in test mode, a simulated NetBox seeded with sample data, so you can evaluate the full workflow before pointing it at production.
What Maps to What
Each Aravolta entity maps to its natural NetBox object. Aravolta resolves related objects by name (sites, racks, roles, device types, tenants) using NetBox's own lookup semantics, and primary IPs are find-or-created in IPAM and assigned through device interfaces the way NetBox requires.
asset.name -> device.name manufacturer -> device_type.manufacturer model -> device_type.model role -> device.role serial number -> device.serial datacenter -> device.site cabinet -> device.rack tenant -> tenancy.tenant ip address -> ipam.ip-address (primary_ip) custom properties -> device.custom_fields
A cross connect can span several hops, so it becomes one NetBox cable per segment, terminated on the rear or front ports it connects. If NetBox rejects a write, that entity is reported with NetBox's validation message and retried on the next pass while the rest of the topology keeps syncing.
Watch Push Sync Run
This is a live simulation of push sync inside Aravolta. Press Push to NetBox and watch each entity move from queued to synced in dependency order, then select any row to see the exact request Aravolta sends and the Aravolta id it stamps.
Aravolta keeps nine entity types in sync with NetBox:
| Aravolta entity | NetBox object | Status |
|---|---|---|
01AmsterdamDatacenter | Sitedcim/sites | Queued |
02Acme CorpTenant | Tenanttenancy/tenants | Queued |
03AMS01 Hall ARoom | Locationdcim/locations | Queued |
04AMS01 Cage 3Zone | Locationdcim/locations | Queued |
05AMS01-RK-01Cabinet | Rackdcim/racks | Queued |
06AMS01-LEAF-39Asset | Devicedcim/devices | Queued |
07LumenInternet provider | Providercircuits/providers | Queued |
08AMS01-PP-01 : A1Patch panel port | Rear / front portdcim/rear-ports | Queued |
09XC-AMS01-0042Cross connect | Cabledcim/cables | Queued |
POST /api/dcim/devices/
{
"name": "AMS01-LEAF-39",
"role": { "name": "Access Switch" },
"device_type": {
"manufacturer": { "name": "Juniper" },
"model": "EX4300-48P"
},
"site": { "name": "Amsterdam" },
"rack": { "name": "AMS01-RK-01" },
"tenant": { "name": "Acme Corp" },
"serial": "PE3716040123",
"custom_fields": { "aravolta_asset_id": "111707" }
}Changes are captured automatically and pushed in dependency order, so sites, tenants, locations, racks, devices, providers, ports, and cables all land with their references already in place. Select any row to see the request Aravolta sends.