https://api.meraki.com/api/v0/networks/L_646829496
481099586/devices. You populate the two headers
Accept and X-Cisco-Meraki-API-Key with their
respective values, select the GET method, and click the
Send button. If everything went well, the response code
should be 200 OK, and the body of the response should
contain exactly the same information found using curl.
Figure 8-3 shows the Postman client interface with all
the headers and fields needed to get a list of all devices
that are part of the network with ID
L_646829496481099586.
Figure 8-3 GET Devices REST API Call in Postman
So far, you have explored the Meraki Dashboard API
using curl and Postman. You first obtained the
organization ID of the DevNet Sandbox Meraki account
and then, based on that ID, you obtained all the networks
that are part of the organization and then used one of the
network IDs you obtained to find all the devices that are
part of that specific network. This is, of course, just a
subset of all the capabilities of the Meraki Dashboard
API, and we leave it as an exercise for you to explore in
more depth all the capabilities and functionalities of the
API.
As a final step in this section, let’s take a look at the
Meraki Python SDK. As of this writing, there are two