"softwareType" : "Cisco Controller",
"associatedWlcIp" : "",
"instanceUuid" : "50c96308-84b5-43dc-
ad68-cda146d80290",
"interfaceCount" : "8"
},
... omitted output
],
"version" : "1.0"
}From this verbose response, you can extract some very
important information about the network devices
managed by Cisco DNA Center. The data returned in the
response is too verbose to fully include in the previous
output, so just a snippet is included for your reference.
As of this writing, in the complete response output, you
can see that there are 14 devices in this network:
One AIR-CT3504-K9 wireless LAN controller
One WS-C3850-24P-L Catalyst 3850 switch
Two C9300-48U Catalyst 9300 switches
Ten AIR-AP141N-A-K9 wireless access pointsFor each device, you can see extensive information such
as the hostname, uptime, serial number, software
version, management interface IP address, reachability
status, hardware platform, and role in the network. You
can see here the power of the Cisco DNA Center platform
APIs. With one API call, you were able to get a complete
status of all devices in the network. Without a central
controller like Cisco DNA Center, it would have taken
several hours to connect to each device individually and
run a series of commands to obtain the same information
that was returned with one API call in less than half a
second. These APIs can save vast amounts of time and
bring numerous possibilities in terms of infrastructure
automation. The data returned by the API endpoints can
be extremely large, and it might take a long time to
process a request and return a complete response. As
mentioned in Chapter 7, pagination is an API feature that