Cisco Meraki Dashboard Access vs API Access Explained

Cisco Meraki Dashboard Access vs API Access Explained

When configuring Cisco Meraki monitors in Site24x7, the API endpoint used determines whether the request is treated as API access or Dashboard access. If the incorrect allowlist is configured, API requests may fail even though authentication details are valid.
This article explains the difference and how to correct the configuration.

Understanding the difference between Dashboard Access and API Access

In Cisco Meraki environments, IP allowlisting is typically separated into two categories:

  1. Dashboard Access

    If the endpoint is configured as a dashboard node (such as n123.meraki.com):

    1. Requests are treated as Dashboard Access.
    2. The monitoring system’s IP addresses must be allowlisted under Dashboard Access.

    These endpoints are typically associated with dashboard sessions or node-specific access.

  2. API Access

    If the monitoring configuration uses the base API endpoint (api.meraki.com):

    1. Requests are treated as REST API calls.
    2. Only API Access allowlisting is required.
    3. Dashboard Access allowlisting is not required

    This endpoint is commonly used by monitoring tools, automation scripts, and integrations that interact with the Meraki REST API.

Common misconfiguration

A common issue occurs when:
  1. Monitoring is configured using a link (like n123.meraki.com).

  2. However, the monitoring system IPs are allowlisted only under API Access. 
In this case, API calls fail because the requests are evaluated against the API Access allowlist.

Impact of incorrect configuration

When IPs are added only under Dashboard Access:
  1. Web portal login works as expected.
  2. API calls from external systems fail.
  3. Data collection or synchronization does not occur.
  4. Errors such as authentication failure or connection timeout may appear.

Resolution steps

To correct the configuration:
  1. Log in to the Site24x7 application.
  2. Navigate to SDN > Meraki. Then, click the required monitor. 
  3. Click the hamburger icon  beside the monitor name, then click Edit.

  4. Click Change Meraki API Endpoint. 

  5. Update the Meraki API URL and click Test.
  6. Close the pop-up window, then click Save.

Best practices

  1. Always confirm which endpoint is used in the monitoring configuration.
  2. Ensure monitoring system IPs are added to the correct allowlist based on the endpoint type.
  3. Test API connectivity after updating IP allowlists to confirm successful communication.