Webinar August 20th at 11:00 am GMT-4 (that’s All of us eastern DST), Register now.

I’ve been dealing with Meraki for about three years today and I’ve always believed the Dashboard API (edition 0 or v0) had been clever within its implementation. Initially, Meraki additional in the API to meet up customer requests. Although majority of the execution felt “API initial” some nuances pointed out that it had been bolted-on as required. That said, it has verified for years to become a useful tool in system creation, management, and supervising.

Demonstrable ROI

The Meraki Dashboard API has provided a demonstrable ROI for a large number of organizations, saving commitment by permitting them to build systems and applications for exactly how they manage IT. There are numerous types of branch structured agencies (retail, trucking, etc.) that leverage the Dashboard API to create apps that allow on-web site associates to deploy and manage their nearby networks and devices.

Employed in conjunction with DevNet, Meraki followed a good “API First” mentality within the growth of the initial NEW edition of the Dashboard API (v1 as we’re discussing it). Today, Meraki is preparing to unveil the resulting enhancements!

Enhanced Developer Experience

The most known change to the Meraki Dashboard API for v1 may be the documentation. V1 documentation in arranged by hierarchical structure, product then, and function inside a product finally. This enables for a quicker programmer evaluation of API efficiency and gets rid of the guessing game which endpoint outlines up with which Dashboard perform. Subsequent that, the endpoint reference definitions fall consistent with how they are organized in the documentation. Add improved consistency in reaction information formatting and these adjustments give a more streamlined encounter which will speed API implementations.

Increased Efficiency

Among the major problems for new developers within utilizing the Meraki API may be the rate limit. This is often a particular concern when institutions are managing a large number of networks with a huge selection of gadgets that have a large number of clients linked to them. The opportunity to manage that instantly is limited. Nevertheless, with v1, a concentrate was placed on high-volume information retrieval for GET functions allowing a business to reduce down the amount of API phone calls being made. Mix this improvement with Meraki Action Batches and devs might never visit a 429 error again!

Strategic Function Based Access Control

This noticeable change is for all your managed service providers on the market. Meraki historically needed that an administrator utilizing an API Crucial have organization READ gain access to at minimum to utilize the Dashboard APIs. This is a difficult limitation in circumstances where developers should just have had usage of either specific customer systems in a organization or test systems just. With v1, the dashboard APIs is now able to be utilized by administrators which are cordoned to particular networks no organization level entry is required.

Want for more information?

If you’d prefer to learn more and discover some great demonstrations with the brand new version of the API, I’m hosting a webinar on August 20th at 11:00 am GMT-4 (that’s US eastern DST). In this program I’ll review some details of everything you find above and help allow you to get started in relation to adopting Meraki’s brand new version of its amazing API. If you’d prefer to get started dealing with v1 before that, really feel free to browse the new docs on DevNet!

The post Meraki Dashboard API v1 Streamlines the Developer Experience appeared 1st on Cisco Blogs.