strength indicator) values for wireless clients,
authentication time, connectivity and traffic patterns,
and number of DNS requests and responses. In the API
documentation, you can see that the resource providing
the health status of all clients connected to the network is
/dna/intent/api/v1/client-health. This API call requires
a parameter to be specified when performing the call.
This parameter, called timestamp, represents the UNIX
epoch time in milliseconds. UNIX epoch time is a system
for describing a point in time since January 1, 1970, not
counting leap seconds. It is extensively used in UNIX
and many other operating systems. The timestamp
provides the point in time for which the client health
information should be returned in the API response. For
example, if I retrieved the health status of all the clients
connected to the network on Thursday, August 22, 2019
8:41:29 PM GMT, the UNIX time, in milliseconds, would
be 1566506489000. Keep in mind that based on the data
retention policy set in Cisco DNA Center, client data
might not be available for past distant timeframes.
With the information you now have, you can build the
API endpoint to process the API call:
https://sandboxdnac2.cisco.com/dna/intent/api/v1/clie
nt-health?timestamp=1566506489000. The
authorization token also needs to be included in the call
as a value in the X-Auth-Token header. The curl
command should look as follows:
Click here to view code image
curl -X GET \https://sandboxdnac2.cisco.com/dna/intent/api/v1/client-
health?timestamp=1566506489000 \
-H 'X-Auth-Token:
eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.
eyJzdWIiOiI1Y2U3MTJiMDhlZTY2MjAyZmEyZWI4ZjgiLCJhdXRoU291cmNlIjoiaW50ZXJuYWwiLCJ0ZW5hbnROYW1lIjoiVE5UMCIsInJvbGVzIjpbI