TM Forum-compliant network APIs
Exposes the network through standards-based APIs compliant with TMF638, TMF639 and TMF640, enabling seamless OSS/BSS and AI integration and smarter monetization of the network as an API.
NAPI learns a device from its IP address in about two minutes, exposing legacy and modern multi-vendor networks through one AI-ready API layer.
NAPI architecture ready
NAPI use cases
One vendor-neutral control plane supports device discovery, live state, service intent, validation and activation through the same governed API flow.
Automatically generates device-specific templates and applies validated configurations across multi-vendor networks, with no-code workflows and syntax-aware intelligence.
Translates high-level service intent into executable workflows using service templates, resource templates and state models across multi-domain networks, working hand in hand with Digi-Twin's real-time network insight.
Zero-touch service activation linking service requests to real-time device status, configuration and dependencies, with full validation to reduce order fallout and activation latency.
Connects across SSH, SNMP, REST, NETCONF, TL1 and SOAP using an AI-driven engine to detect device types, capabilities and configuration, normalizing real-time topology and telemetry into a vendor-agnostic model.
Abstracts complex, vendor-specific network information into a unified model exposed through TMF638/639/640, so AI agents, OSS/BSS and external systems integrate without vendor-specific code.
Core capabilities
A layered architecture hides vendor differences while preserving operator policy, open API support, audit detail and deployment control.
Exposes the network through standards-based APIs compliant with TMF638, TMF639 and TMF640, enabling seamless OSS/BSS and AI integration and smarter monetization of the network as an API.
Configure and manage services by entering required inputs through a guided UI, no scripting or coding required.
Built-in support for 100+ device types across vendors, domains and protocols (SSH, TL1, SOAP, SNMP, REST, NETCONF) through AI-generated, template-driven integration.
Supports multi-domain environments, transport, core and access, across wired and wireless infrastructure, for unified management regardless of technology or vendor.
Out-of-the-box connectivity
Each connector follows one Integration Hub contract, preserves raw replies for replay and extends vendor coverage without changing the core platform.
How it works
NAPI securely connects, discovers, models, validates and activates network devices while keeping live state available through one API-driven workflow.
{
"id": "juniper-mx-480",
"vendor": "Juniper Networks",
"product": "JUNIPER-MX-480",
"version": 7,
"childConfigs": [
"snmp/device/juniper-mx-480/conf",
"snmp/inventory/if-mib.conf",
"snmp/inventory/ip-mib.conf",
"snmp/topology/lldp-mib.conf"
],
"collectFault": true
} {
"cpu": {
"cpuUtilization": "string"
},
"temp": {
"temperature": "string"
},
"memory": {
"memoryUsed": "string"
},
"pollInventory": true,
"pollPerformance": true
} Integration Logs
12:26:01 · Pinging 192.168.100.129 with packet 12:26:02 · Host 192.168.100.129 is NOT reachable (ping failed with return code 1).Connect Branch A and B
with 1 Gbps Layer 3 VPN
Status: Success Service ID: L3VPN-A-B-20250817 Activation Time: 2025-08-17 10:32 AM IST Bandwidth: 1 Gbps
Success Failure Skipped
Total Handled To be Handled Failed
CiscoJuniperHuaweiNokiaDell
Total Handled
VoiceVideoData
In production
Validated automation replaces fragile scripts with faster recovery, repeatable migration and an accurate view of changing multi-vendor networks.
Fallout
3× faster recoveryMigration
70% fasterDiscovery
100% accuracy"NAPI enabled us with full network visibility in hours, not weeks, uncovering blind spots and simplifying management across legacy and modern devices."
Head of Network Automation, US Telecom Operator
NAPI · Network Orchestrator