I don't believe we did.  ... View more

Okay, thanks John.  ... View more

Do you know if the docs have always stated they are opaque?  ... View more

But the API spec didn't change from what I can tell. It was the contract for the API but it was behavior of the formatting of the URL that came back and I don't think that's part of the spec.  ... View more

Thanks Jon. Is there a newsletter or notification for API changes we can subscribe to? This has turned into a mess for us as this broke the integration for our customers. I had never concerned myself with it before now because I was under the impression that nothing would change in the API behavior unless it happened as a versioned change in a v2 URL for example. I assumed something we built for the v1 API would continue to work.  ... View more

I have also noticed similar oddities in that API call and even had a teammate submit a question about that before. I'm asking on behalf of a customer using our integration so I'll have to have them dig into it. Thanks for the information! I'll report back if I find anything.  ... View more

I don't see a "total" value in this response, so I presume you are making a separate API call to fetch that, correct?    https://developer.cisco.com/meraki/api-v1/get-organization-devices-uplinks-loss-and-latency/   While this makes sense, that's disappointing if that's the only workaround as that's added complexity I'd like to avoid.  ... View more

Thanks. This was posted by someone on my team. We aren't a customer, but a partner building this out for a customer. I'm not sure we are able to open support cases on behalf of our customers.  ... View more