jViNmNmZGZmNDMwOTkwMDA4OWYwZmYzNyJdLCJ0ZW5hbnRJZCI6IjViNmNmZG-ZjNDMwOTkwMDA4OWYwZmYzMCIsImV4cCI6MTU2NjYxODkyOCwidXNlcm5hbWUiOiJkZXZuZXR1c2VyIn0.7JNXdgSMi3Bju8v8QU_L5nmBKYOTivinAjP8ALT_opw'The API response should look similar to Example 8-6.
From this response, you can see that there are a total of
82 clients in the network, and the average health score
for all of them is 27. To further investigate why the
health scores for some of the clients vary, you can look
into the response to the /dna/intent/api/v1/client-detail
call. This API call takes as input parameters the
timestamp and the MAC address of the client, and it
returns extensive data about the status and health of that
specific client at that specific time.
Now you can try to perform the same API call but this
time with Postman. The API endpoint stays the same:
https://sandboxdnac2.cisco.com/dna/intent/api/v1/clie
nt-health?timestamp=1566506489000. In this case, you
are trying to retrieve information from the API, so it will
be a GET call, and the X-Auth-Token header contains a
valid token value. Notice that the Params section of
Postman gets automatically populated with a timestamp
key, with the value specified in the URL:
1566506489000. Click Send, and if there aren’t any
errors with the API call, the body of the response should
be very similar to the one obtained previously with curl.
The Postman window for this example should look as
shown in Figure 8-9.