Meraki

Oren · Re: NOTICE: Unsupported base URIs will stop working September 15, 2025

UPDATE 2: Per the community's requests, we are postponing enforcement of blocking undocumented base URIs to November 17, 2025 at 9:00 AM Pacific (1600h UTC). Please use this extra time to update your code to use only documented base URIs.

Oren

Hi everyone, Based on feedback we heard from multiple people, we are consolidating the two Meraki Terraform providers out there. The old provider (cisco-open/terraform-provider-meraki) is deprecated and will no longer be updated. The new provider (CiscoDevNet/terraform-provider-meraki) is now the official, actively maintained version. Why is this change happening? The new Terraform provider will provide more efficient operations, ongoing support, new features, and improvements, ensuring a more robust and future-proof experience for all Meraki users. Can I continue using the old provider? Yes, but the old provider will no longer receive updates or new features. We encourage you to plan a migration to the new provider. Bugs will be fixed on a best effort basis until January 31st, 2026. What are the recommended migration steps? Review Documentation: Read the new provider’s documentation carefully. Resource names and attributes are not necessarily the same. Update Configurations: Refactor your .tf files to match the new HCL format and attribute names. Test Plans: Run terraform plan to identify required changes and resolve any errors. Handle State: Use terraform import or state manipulation commands to align existing resources with the new provider’s resource model. Validate Changes: Test in a non-production environment before applying changes in production. What happens if I don’t migrate? Your existing setup will continue to function, but no new features will be available for this provider. Over time, compatibility issues may arise as Terraform and Meraki evolve. Bugs will be fixed on a best effort basis until January 31st, 2026.

Oren

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

Oren

Since rate limit hits is off the table, and an API call using Postman is updating the port immediately - I wonder when does Forescout make the API call to make the configuration change. You can test it yourself. Trigger a port to change the vlan (via Forescout), wait for it to update, then - download the API logs (upper right button on the API page) and look for an API call make to the relevant switchport (you can filter the calls based on the URL). If the API call was made in a timely manner, and was successful - that's a question for Meraki support. If the API call was made after some time - that's a question for Forescout. Good luck!

Oren

12 hours does not seem reasonable by any mean.. Question. If you make an API call using postman/curl/python - how long does it take for the port configuration to update? I have a suspicion. Your organization ID or serial number of one of the switches will allow me to confirm it (you can DM it if you prefer).

Oren

I’d start with getOrganizationDevices that will retrieve the longitude and latitude of each device.

Oren

Sounds like a classic use-case for a sprinkle of API magic. You can choose the tool you feel most comfortable with: Python, Ansible, Terraform, or Cisco Workflows (low code/no code automation built into the Dashboard). You will want to start by listing the networks in the organization, then you’ll want to iterate through the list (“for loop” if it’s Python) and make an API call to get the MQTT settings for each network ID). ChatGPT/copilot can help - they might make mistakes in the process.

Oren

Sounds like a good reason to open a support case. What is the API call you're trying to make?

Oren

Yes 😉

Oren

The Network Automation Forum is running a survey to fuel their upcoming “2025 State of Network Automation Report.” The best part? You don’t have to be automating everything in sight to participate - if you operate a network (or occasionally bribe it with coffee), you qualify. I’m really curious to see what insights this year’s report uncovers. If you can spare a few minutes - less than the time it takes for your switch to reboot - please share your feedback. 👉 https://www.surveymonkey.com/r/StateOfNetworkAutomation_2025 Your future network may thank you with fewer 2 a.m. alerts. All responses are anonymous, and only aggregate data will be published by the Network Automation Forum. I have no affiliation with NAF other than reading their content.

Oren · Re: NOTICE: Unsupported base URIs will stop working September 15, 2025

UPDATE: Per the community's requests, we are postponing enforcement of blocking undocumented base URIs to October 17, 2025 at 9:00 AM Pacific (1600h UTC). Please use this extra time to update your code to use only documented base URIs.

Oren

Yep. Can you kindly provide an example of a script using aio what makes more than 10 calls/sec? cc: @John_on_API

Oren · ‎Sep 10 2025

Great question, Philip. MCP stands for Model Context Protocol. Think of MCP as a "USB-C port for AI applications" or an "API for APIs" for LLMs. Similar to how our Python SDK makes it easier for Python developers to consume our APIs, MCPs allow LLMs (like ChatGPT, Claude, Gemini, etc') to leverage our APIs. Gabi created multiple interesting demos and concepts unlocked by the (relatively) new technology.

Oren · ‎Sep 9 2025

Thanks for reporting this. Kindly create an issue on the Ansible collection's GitHub repo and the team will get it fixed.

Oren · ‎Sep 9 2025

It will be a 308 Permanent Redirect.

Oren · ‎Aug 30 2025

Would you like to try the Meraki Python SDK? It will mask most of the lower level tweaks and help minimize mistakes.

Oren · ‎Aug 29 2025

I wonder if the energy management dashboard that's about to become available will provide the information you're looking for.

Oren · ‎Aug 21 2025

Most likely, device availabilities in the relevant successor, but check our deprecation page: https://developer.cisco.com/meraki/api-v1/deprecated-operations/#deprecated-operations. We will have the deprecation banner refer to this page for easier discoverability. I hope this helps.

Oren · ‎Aug 21 2025

Thanks for reporting. Can you check if you're still getting an error?

Oren · ‎Aug 13 2025

I might have mixed it with a similar operation. Let me take the feedback with the team, and we'll try to find a way to address it.

Oren · ‎Aug 13 2025

Thanks for the feedback, @RaphaelL. This operations is still in beta and not widely used yet, which means we can still influence and enhance it to address your comments. I'll make sure the relevant team takes your feedback into consideration.

Oren · ‎Jul 23 2025

The API call you are trying to make would return aggregated information, I don’t see much difference. Can you perhaps explain the use-case, the data you’re trying to obtain, and how it would be used?

Oren · ‎Jul 23 2025

I see. Assuming you’re using the same timespan, maybe one of these clients had no traffic during that time. If you’re listing all clients, would it make more sense to use getNetworkTraffic?

Oren · ‎Jul 22 2025

Can you share the case number? Or a specific API request that would result in a 400 error, so I can take a look.

Oren · ‎Jul 22 2025

Yaakov, did you open a support case about this problem?

About Oren

Oren

Community Record

Badges