Meraki Dashboard API
Access to your Cisco Meraki cloud-managed in a pythonic way. Also available via PIP
Prerequisites
You need to enable APIs in your Meraki dashboard and obtain an APIKey: Instructions
Example
from meraki_dashboard_api import Dashboard
apikey = "jkhsfsdhk32424******example*****jlasdfsdfl3245345"
dash = Dashboard(apikey)
# list all organizations
myOrgs = dash.organizations.list()
print(myOrgs)
# list all organization's networks
myNets = dash.organizations.networks(<orgId>)
print(myNets)
Since the other options available are complex or old school, my need was a more pythonic and object oriented way.
The 90% of que API belong to the /networks endpoint and from there appears some groups, in the Meraki documentation these groups are represented as isolated, but most of them belong to the same parent endpoint.
The oficial implementation is a simple functional programming (old school) and the guzmonne implementation is, I think, a really complex approach returning instances inside another instances.
Ex:
response = meraki.organizations().index()
json = response.json()
Instead I use some magic methods to instantiate the classes following a strict URL pattern.
Ex:
client = dash.networks.clients.get(<networkId>, <clientId>)
print(client)
I use args to build the URL path and kwargs to pass query parameters each endpoint .
Ex:
dev = dash.networks.devices.loss_and_latency(<networkId>, <serial>, uplink=‘wan1’, ip=‘1.2.3.4’, timespan=7200)
print(dev)
For POST and PUT methods you can use a kwargs data or update.
Ex.
payload = {
'name': 'My AP',
'tags': 'recently-added ',
'lat': 37.4180951010362,
'lng': -122.098531723022,
'address': 'some place',
'notes': 'no notes',
'moveMapMarker': True
}
dev = dash.networks.devices.update(<networkId>, <serial>, update=payload)
print(dev)
Metadata
Release files for meraki-dashboard-api 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| meraki-dashboard-api-1.0.0.tar.gz | 10.8 kB | Without provenance | Details for meraki-dashboard-api-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| meraki_dashboard_api-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for meraki_dashboard_api-1.0.0-py3-none-any.whl |
Total release size: 25.5 kB
Release files / meraki-dashboard-api-1.0.0.tar.gz
| Download URL | meraki-dashboard-api-1.0.0.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5710a77047c4a6d86cb2b2b1dc5ebbf429339a7f701f4b7162d7ce48bc9aea76
|
|
BLAKE2b-256 checksum How to use checksums |
b137068172dd82568aa917747caa27728c933b4b1d49f94d3c1bb2f200f8c246
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.7.3 requests-toolbelt/0.9.1 tqdm/4.30.0 CPython/3.7.2
|
Release files / meraki_dashboard_api-1.0.0-py3-none-any.whl
| Download URL | meraki_dashboard_api-1.0.0-py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
967723ab393aa25d23b398ceb087dd118a9517d4cea55e160400d58a6a84dd2e
|
|
BLAKE2b-256 checksum How to use checksums |
448bb689ff2aae3f12caf3a831d0b4a8b13f7dd75e686e2fd4c2b47d93d4a014
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.7.3 requests-toolbelt/0.9.1 tqdm/4.30.0 CPython/3.7.2
|
Security for meraki-dashboard-api 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.