Introducing Push API public beta 🤖

obrigg — Tue, 01 Sep 2026 17:53:19 GMT

We’re excited to announce the public beta of Push API, an event-driven alternative to repeatedly polling the Meraki Dashboard API.

API rate limits can make frequent polling difficult to scale, especially as network environments grow. Push API enables you to subscribe to supported topics and receive near-real-time updates through webhooks - helping reduce polling volume and preserve API capacity for other operational needs.

How it works

You configure an HTTPS webhook endpoint and subscribe your organization to a topic. When a qualifying change occurs - such as a device becoming unavailable or a configuration update - Meraki sends the event to your endpoint via an HTTP POST. Your application can process the update immediately instead of waiting for the next scheduled poll.

Push API also sends a Heartbeat message every five minutes, even when there is no event to report. This gives your system a regular signal that the delivery path is active.

The initial public beta includes:

Device availability changes
Configuration changes

To learn more and try Push API, visit the Push API documentation. We welcome your feedback and would be interested to hear how Push API could support your use cases.

Re: Introducing Push API public beta 🤖

Raphael_L — Wed, 02 Sep 2026 01:49:57 GMT

Big step forward ! Congrats Oren and your team, impressive work as usual !

Re: Introducing Push API public beta 🤖

Noel-Edouard Chenu @ Boundless — Mon, 07 Sep 2026 08:47:25 GMT

This is the right direction and I'm glad to see it public. Polling has been the tax on every multi-org integration we've built: you either burn rate limit budget keeping data fresh or you accept stale data. Neither is great at 50+ orgs.

topic Introducing Push API public beta 🤖 in Network Platform API

Introducing Push API public beta 🤖

How it works

Re: Introducing Push API public beta 🤖

Re: Introducing Push API public beta 🤖