> ## Documentation Index
> Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Scanning Cisco Meraki

> Capturing Cisco Meraki through an API key – no targets, no target columns, no module options.

The *Cisco Meraki* module addresses no addresses in your network. Instead it needs an
API key – and therefore nothing you would have to enter target by target.

The wizard shows four steps for this module:

*Basics* › *Authentication* › *Schedule* › *Summary*

All but *Authentication* are the same for every module – see
[Creating a Scan Job](/docs/en/scan/create-inventory). A connected
[gateway](/docs/en/scan/gateway-install) is required.

## The key

Here the *Authentication* step carries no Windows credentials but the
*Meraki API Key* – that is what the line below the step name calls it. The entry
for it has the type *API Key* and consists of a single, masked field. You choose
it in the same searchable picker as with the other modules and create missing
ones through *New credentials…* or *One-time credentials…* directly here. Entries
of this type are managed under *Scan › Credentials*.

<Note>
  Unlike with *Active Directory* and *Windows (AD)*, credentials are **mandatory**
  here: without an entry the step cannot be passed.
</Note>

## Without targets or options

This module carries no table with targets. The *Customize* button does not appear
here either: *Cisco Meraki* brings no options of its own.

That leaves only the scheduling to be decided for the job.

## Related

Which types this scan produces is under
[Network and Devices](/docs/en/assets/network-devices). How you watch the job
afterwards is in [Managing Jobs](/docs/en/scan/manage-jobs).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.