Enable API access endpoint

[Abn]

Hi,

I worked with an MSP and my goal is to loop through the organizations we manage and standardize some alert settings and stuff. The logic is built but I realized that most of the organizations do not have API access enabled hence it throws back the response " {'errors': ['To make requests you must first enable API access via https://n345.meraki.com/o/jKy789/manage/organization/edit']}'

is there an endpoint to help me enable API access for an organization?

[Inderdeep]

Check this link below if it helps 

https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API#:~:t....

[Abn]

That doesn't help but I appreciate. I want the endpoint that can allow me to enable the dashboard API.

[Inderdeep]

Check this one 

https://developer.cisco.com/meraki/api/#!get-organization-api-requests

[Abn]

Per my problem, I am expecting a PUT/POST method. 

[Inderdeep]

May be first you need to create the Org Access as full and then you can do that changes on the dashboard. Never tried 

https://developer.cisco.com/meraki/api/#!create-organization-admin

[PhilipDAth]

There is no way an API can exist to enable API access.

No such endpoint exists, or will ever exist.

[AutomationDude · Accepted solution]

I understand your problem, but you are unfortunately in a paradox 😔

You're trying to tell your orgs to do something with the APIs, but how could this ever be possible when the APIs aren't enabled? 

Now it would be theoretically awesome if there was one such API touchpoint that acted as kind of gate for the other touchpoints, but the security risk would be too immense for this to ever happen and it also probably wouldn't make sense 😄

I'm afraid you'll have to do this one thing the old school way!

[Abn]

Well, I thought that once I have the master account for managing multiple Orgs under MSP portal, I could just use the API key of the MSP to enable all the children Orgs.

Sure, I will do the old school way. Thanks 😊

[John_on_API]

You can now enable API on orgs via API, as long as you are an org admin on those organizations where you'd like to enable API. 

See: https://developer.cisco.com/meraki/api-v1/#!update-organization

It's not a valid security concern.

• Org admins are org admins--they either have the keys to the kingdom, or they aren't org admins. You should only add folks you trust as org admins. 
• There's nothing inherently more secure about disabling API access, in any case. API access is not a form of RBAC; API keys inherit the privileges of the associated user.
• If someone is an org admin in your organization, then they could have just used the GUI to enable API access in your org, no API required, if they so wanted.
• Finally, there are very real efficiency benefits of being able to manage this via API, which you can't realize via any other method, especially for enterprise and MSP deployments where API is the customer's chosen primary user interface.