Merakifly Integration Guide


This guide outlines the steps required to integrate our solution with Cisco Meraki. The integration involves providing essential details such as the Meraki API key, organization ID, vendor name, etc. 

Step-by-Step Integration 

1. Obtain the Meraki API Key 

To use the Meraki Dashboard API, you need an API key. Here’s how you can get it: 

  1. Log in to the Meraki Dashboard 
  2. Navigate to Organization > Settings 
  3. Under API access, generate a new API key 
  4. Copy and store the API key securely. It will be used for authentication in API requests 

2. Find Your Meraki Organization ID 

The organization ID is necessary for making API calls related to your Meraki organization: 

  1. In the Meraki Dashboard, navigate to Organization > Overview 
  2. The organization ID is part of the URL. For example, in, 12345 is the organization ID 

3. Configure the Vendor Name 

Provide the vendor name that will be used to identify the integration source. Ensure it matches the name registered with your Meraki account. 

4. Ticket Service Requirements 

The ticket service is where Merakifly will send alert notifications. Ensure your service is set up to handle incoming requests from Merakifly. 

JIRA Integration 

If your ticketing system is JIRA, you need to provide the following details: 

  • JIRA Base URI: The base URI of your Jira instance (e.g., 
  • JIRA Project Key: The project key where tickets will be created 
  • Username/Password: For authentication purposes 
  • Issue Type: The type of issues to be created (e.g., Bug, Task) 

5. Auth Service Requirements 

If your authentication service uses Single Sign-On (SSO), you need to provide the following information: 

  • Client ID: The application ID for your app registered in Azure AD 
  • Client Secret: A key associated with the application 
  • Tenant ID: Your Azure AD tenant ID 
  • Set the Redirect URL in Azure AD: Add the redirect URL (e.g., https://(merakifly-app-url)/auth/verification) under the “Redirect URIs” section to which Azure AD will send responses after user authentication 


If you encounter any issues, please contact our support team @