Dashboard API v1 supports Bearer Auth using the standard Authorization header parameter. The value will be a string that begins with the word Bearer, followed by your Meraki API key.

Note: When developing scripts, it's a best practice to create a local environment variable MERAKI_DASHBOARD_API_KEY and set it to your API key, so that you can omit it from your source code. Instructions vary by operating system, so please consult your OS vendor for more information.

 "Authorization": "Bearer <API_KEY>"
curl \
  -L -H 'Authorization: Bearer {API_KEY}'
# Example 1: Best practice
# This example will read the local environment variable `MERAKI_DASHBOARD_API_KEY`
# so that you don't have to add it to your source code. Please see above if you
# haven't already created this environment variable.
import meraki
dashboard = meraki.DashboardAPI()

# Example 2: Riskier
# Defining your API key as a variable in source code is not recommended. Please
# consult the above regarding best practices.
import meraki
API_KEY = '6bec40cf957de430a6f1f2baf056b99a4fac9ea0'
dashboard = meraki.DashboardAPI(API_KEY)

Obtaining your Meraki API key

In order to interact with the Dashboard API, you must first obtain an API key.

  • Open your Meraki dashboard:
  • Once logged in, navigate to the Organization > Settings page.
  • Ensure that the API Access is set to “Enable access to the Cisco Meraki Dashboard API”

Then go to your profile by clicking on your account email address (on the upper-right) > My profile to generate the API key.

save this key in a secure location, as it represents your admin credentials


If you get a 401 Unauthorized error (with message "Missing API key") when using dashboard API v1 with Bearer token, check the following to troubleshoot:

  1. As an example, when using your API key to retrieve the GET /organizations operation, you should see the same data as shown when navigating to in your browser, using an authenticated session with the credentials that generated the API key.

  2. Next, check that your API call has the correct header with the following (and not v0's X-Cisco-Meraki-API-Key):

Authorization: Bearer {API_KEY}
  1. If making the API call in cURL, check that the --location-trusted flag is included.

  2. If making the API call in Postman, check that the setting “_Follow Authorization header_” is enabled.

  3. If using the Python library, authorization is handled automatically, so assuming the right API key is supplied, the Python code snippet for getOrganizations > Template > Meraki Python Library will work w/ the v1 library installed.

  4. If you really want to write your own functions in Python, then you will need to define a new instance of the requests.Session class that does not rebuild_auth upon a redirect. For example:

from requests import Session
class NoRebuildAuthSession(Session):
    def rebuild_auth(self, prepared_request, response):
      No code here means requests will always preserve the Authorization header when redirected.
      Be careful not to leak your credentials to untrusted hosts!
session = NoRebuildAuthSession()
API_KEY = '6bec40cf957de430a6f1f2baf056b99a4fac9ea0'
response = session.get('', headers={'Authorization': f'Bearer {API_KEY}'})
  1. If using PowerShell with Invoke-RestMethod, make sure that the -PreserveAuthorizationOnRedirect flag is included.

  2. The behavior here is standard and due to API clients like cURL and Postman stripping the Authorization header, for security purposes, when following an HTTP redirect.