API integrations - unsupported base Uniform Resource Identifiers (URIs)

[pfoster]

Anyone have insights? I've had a case open with Meraki for over a week and still no luck. I'm in the US, and got a message that some of our API integrations need to be updated.

Old API - https://nxxx.meraki.com

Supposed new API - https://api.meraki.com/api/v1/

Tried every variation of the above, still no luck.

I'm not versed in API's and such, just trying to get it working. Every time I paste what I thought would be the correct new URL, and test, it fails.

I've tried the following

https://api.meraki.com/api/v1/organizations/nxxx

https://api.meraki.com/api/v1/organizations/

https://api.meraki.com/api/v1/

https://api.meraki.com/

https://api.meraki.com

Anyone have any insights?

[Oren]

Insights to what? Which script is making API calls to an unsupported URI, or how to update it?

[alemabrahao]

First, you'd need to verify which APIs you use and then check not only the initial URL, but also validate the corresponding API for the function you're using.

This would be a good place to start.

https://developer.cisco.com/meraki/api-v1/introduction/#meraki-products

[sungod]

Your "Old API" is pointing at a specific shard nxxx, I don't think referencing a shard has ever been advocated as the base URI (other than as a workaround for some problems a while ago), it generally works, but it's not the proper way.

In most parts of the world, every API request should begin with the following base URI:

https://api.meraki.com/api/v1

...this has been the standard for many years now.

The recent change is that for organizations hosted in the following dashboards, you need to specify the respective base URI instead:

Dasboard/Country                               URI

Canada	https://api.meraki.ca/api/v1
China	https://api.meraki.cn/api/v1
India	https://api.meraki.in/api/v1
United States FedRAMP	https://api.gov-meraki.com/api/v1

What failure code(s) are you getting?

[pfoster]

Hi All, so I was able to get it working. I replaces https://nxxx.meraki.com with https://api.meraki.com and it worked. I would have got this working sooner, but after the initial testing I realized my firewall rule (Palo Alto) was URL based and whereas I was permitting nxxx.meraki.com I was blocking the new link. BTW, the app I was working with was NetBrain. I have API integrations with NetBrain, ServiceNow, SolarWinds, StatSeeker. 

[Oren]

I'm glad to hear. Thanks for the update!

[PhilipDAth]

Are you able to post the complete URL you are using, or show the code that is forming a full URL (make sure you don't show any API keys)?