authentication purposes. This header will contain the
API key for the DevNet Sandbox Meraki account. The
curl command should look as follows in this case:
Click here to view code image
curl -I -X GET \
--url
'https://api.meraki.com/api/v0/organizations' \
-H 'X-Cisco-Meraki-API-Key:
15da0c6ffff295f16267f88f98694cf29a86ed87'The response should look as shown in Example 8-1.
Example 8-1 Headers of the GET Organizations REST
API Call
Click here to view code image
HTTP/1.1 302 Found
Server: nginx
Date: Sat, 17 Aug 2019 19:05:25 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Cache-Control: no-cache, no-store, max-age=0,
must-revalidate
Pragma: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
X-Frame-Options: sameorigin
X-Robots-Tag: none
Location:
https://n149.meraki.com/api/v0/organizations
X-UA-Compatible: IE=Edge,chrome=1
X-Request-Id: 87654dbd16ae23fbc7e3282a439b211c
X-Runtime: 0.320067
Strict-Transport-Security: max-age=15552000;
includeSubDomainsYou can see in Example 8-1 that the response code for
the request is 302. This indicates a redirect to the URL
value in the Location header. Redirects like the one in
Example 8-1 can occur with any API call within the
Dashboard API, including POST, PUT, and DELETE. For