Note: You shouldn't have to generate any new API keys. We manage all of our clients from a single Meraki instance, and they all use the same API key. The first part of this guide (Steps for generating an API Key in Meraki) is merely for informational purposes.
READ THE NOTE ABOVE BEFORE PROCEEDING.
Pre-requisites:
You MUST use the Advisory Meraki Admin account to generate an API key
Under the API access section, click the Generate new API key button
IMPORTANT: You can only have two active API keys at a single time. If two already exist, do not revoke one of them. Check with your fellow engineers to see what they're being used for before revoking an in-use key.
If successful, you should see a window like the following:
Lastly, copy the newly generated API key since you'll need it for Wizarrd.
Navigate to Organization → Settings under Configure
IMPORTANT: Verify that the checkbox next to Enable access to the Cisco Meraki Dashboard API is checked.
Steps for retrieving the client's Org ID in Postman:
Open the Postman app and download the following Collection:
1 attachment
json
Cisco_Meraki.postman_collection.json
1.6KB
Keep this JSON file handy as you will need to return to it in the next step
From inside of Postman, click Import -> Upload Files -> Select the .json file you downloaded in step 1, and click Import
Under the Collections section, select the dropdown next to Cisco Meraki, then select the GET request and click Send
Once those steps are completed, you should now see the successful JSON response. Each section (denoted by curly braces '{ }') of the JSON response represents an individual company that we manage inside of Meraki, and within each section there is an "id". IMPORTANT: For the purposes of Wizarrd, copy the id string between the quotation marks for the company that you're going to import Meraki data for.