Miro · Rate Limits

Miro Rate Limits

Miro REST API enforces per-OAuth-app rate limits. Free apps share a default ceiling; certified apps and verified apps receive higher limits. 429 responses include a Retry-After header. SCIM and audit-log endpoints have their own limits scoped to the enterprise organization.

Miro Rate Limits is the machine-readable rate-limit profile for Miro on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring request.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Productivity, Whiteboard, Visual Collaboration, Diagramming, and SaaS.

4 Limits Throttle: 429
ProductivityWhiteboardVisual CollaborationDiagrammingSaaSRate LimitingQuotasThrottling

Limits

Default OAuth App oauth_app
request · per-minute
published per-app
Default per-app rate ceiling on the REST API; raise by getting the app verified or certified.
Verified/Certified App oauth_app
request · per-minute
published per-app
Verified or certified apps in the Miro Marketplace receive higher per-minute rate limits.
SCIM organization
request
published per-org
Enterprise SCIM endpoint has its own per-org limit.
Audit Logs organization
request
published per-org
Audit log queries are limited per organization; paginate with cursor and avoid re-querying.

Policies

Backoff Strategy
Exponential backoff with jitter; honor Retry-After on 429.
Use Webhooks for Change Detection
Subscribe to board webhooks rather than polling list endpoints.
Get App Certified
Submit your app for verification/certification to raise rate ceilings if you operate at scale.

Sources