# Miro incoming webhooks have no rate limits, says the product team If you are wiring Jira (or anything high volume) into Miro and worrying that tens of thousands of updates an hour will get you throttled, the official answer is no. On Miro's own community forum, the product team confirmed there are no rate limits on incoming webhooks, even though the REST API sits under the 100,000-credit-per-minute cap. Why this matters: the natural assumption is that webhooks ride the same limiter as the REST endpoints. They do not. So the design decision is clear: - High-volume event ingestion: let webhooks take the flood, no throttling needed on your side. - Polling the REST API for the same data URIs that burns your credit budget and gets you 429s. The asymmetry is the gotcha. Plan your integration around it: webhooks for inbound volume, the credit budget reserved for your REST calls.

Context: Miro community forum: product team confirms no rate limits on incoming webhooks On the official Miro community forum, a user running Jira at large scale asked whether Miro's incoming webhooks have rate limits like the REST API, worried about tens of thousands of issue updates per hour hammering the jira-cards integration. Miro's product team answered directly: they do not have such limits with incoming webhooks. So heavy incoming webhook volume is explicitly fine, unlike the credit-limited REST API.