> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/integrations/remove-integration-access/cisco-meraki.md).

# Cisco Meraki: Remove Sprinto Access

Remove the access Sprinto was given in Cisco Meraki. Covers every way Sprinto can be connected to Cisco Meraki and the steps to take in Cisco Meraki for each.

Use this guide to remove the access you gave Sprinto in Cisco Meraki. These steps are done in Cisco Meraki, not in Sprinto. To connect Cisco Meraki to Sprinto again later, see [Cisco Meraki Integration](https://docs.sprinto.com/integrations/overview/cisco-meraki-integration.md).

***

## Dashboard API key <a href="#dashboard-api-key" id="dashboard-api-key"></a>

**How to tell:** Only method: you generated a Dashboard API key and entered it with your base location.

**Who must do this:** The Meraki admin who owns the key; a Full Access organization admin to remove an admin

**What gets removed:** The API key Sprinto used is revoked, and any admin account created only for Sprinto is removed.

### Steps

1. Sign in to the Meraki dashboard as the admin who generated the key Sprinto uses.
2. Go to **Organization** → **Configure** → **API & Webhooks** and select the **API keys and access** tab (or open My Profile from the avatar icon and go to API access).
3. Find the key Sprinto uses (each admin can have at most two) and revoke it.
4. If you created an admin account only for Sprinto, or the key owner has left: a Full Access admin opens **Organization** → **Configure** → **Administrators**, selects that admin and selects Remove Admin.
5. Optional: Delete any saved copies of the key (password manager, notes). This doesn't affect reconnecting.

### Confirm it's removed

The key no longer appears under API keys and access for that admin, and any Sprinto-only admin is gone from Administrators.

{% hint style="warning" %}
An API key works in every organization its admin can access. Revoking it also stops any other script or tool that uses the same key.
{% endhint %}

{% hint style="info" %}
Look for a revoke option on the key's row under **API keys and access**.
{% endhint %}

**Official guide:** [Cisco Meraki documentation](https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Operate_and_Maintain/How-Tos/How_to_Use_the_Cisco_Meraki_Dashboard_API)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/integrations/remove-integration-access/cisco-meraki.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
