Error "Invalid API key. A full (read/write) key is required"

[CS47]

I cannot get the cloud monitoring for catalyst to connect to my dashboard. I get the error "Invalid API key. A full (read/write) key is required."

I cannot find a way in the dashboard to assign different permissions to an API key.

My user has access set to "full" under organization > administrators.

[CS47]

Weird. I waited 15 minutes, I signed out of the dashboard, signed back in, clicked again on the green button in the "Cloud Monitoring for Catalyst" app and it worked this time, no error. I did not change the API key or any settings in the dashboard.

Problem solved.

[obrigg · Accepted solution]

Was this a newly generated API key?
New API keys can take a few minutes to become active.

[zamrzla1228]

No. I created the key almost 24 hours ago.

[CS47]

yes, it was band new, that was probably it. It would be helpful to have a small warning when creating and API key that reads "it can take up to X minutes before this API key becomes active, you may see the error "Invalid API key. A full (read/write) key is required." until the API key becomes fully active".

[keithli]

realized i didn't enable following, after enabled i can generate API key

Enable access to the Cisco Meraki Dashboard API

[ServiceNow_User]

@keithli , can you guide where to find the option to Enable Dashboard API access on the dashbaord.

I can see it the details under Organization settings - below 2 options asking for the IPs
Allow Dashboard and Dashboard API access to these IP ranges
Allow Dashboard API access to these IP ranges

[obrigg]

Since that message was posted, APIs have been enabled by default for all organizations.

What problem are you facing?

[ServiceNow_User]

@obrigg after the Service Graph Connector For Meraki plugin upgrade from 1.3.3 to 1.4.0, facing the below 2 errors

orgStream: Method failed: (/api/v1/organizations) with code: 401 - Invalid API key

Data Stream Action Splitter Step Method failed: (/api/v1/organizations) with code: 401 - Invalid API key

[obrigg]

Interesting. Are you able to make an API call using that API key with Postman or cURL?

[shwpalan]

Hi @ServiceNow_User since you mentioned you have upgraded the plugin, try deleting your API key and pasting it again in the ServiceNow plugin. Let us know if that resolved the issue!