miro-rate-limits

# Miro Rate Limits ## Overview Miro measures API usage in **credits**, not raw request counts. Each endpoint consumes a different number of credits based on complexity. The global limit is **100,000 credits per minute** per app. ## Credit System ### Rate Limit Levels Each Miro REST API endpoint is assigned a rate limit level that determines its credit cost: | Level | Credits per Call | Example Endpoints | |-------|-----------------|-------------------| | Level 1 | Lower cost | GET single board, GET single item | | Level 2 | Medium cost | POST create sticky note, POST create shape, POST create connector | | Level 3 | Higher cost | Batch operations, complex queries | | Level 4 | Highest cost | Export, bulk data operations | The exact credit cost per level is subject to change. Monitor via response headers. ### Rate Limit Response Headers Every Miro API response includes these headers: | Header | Description | Example | |--------|-------------|---------| | `X-RateLimit-Limit` | Total credits allocated per minute | `100000` | | `X-RateLimit-Remaining` | Credits remaining in current window | `99850` | | `X-RateLimit-Reset` | Unix timestamp when window resets | `1700000060` | When rate limited, the response also includes: | Header | Description | Example | |--------|-------------|---------| | `Retry-After` | Seconds to wait before retrying | `30` | ## Exponential Backoff with Jitter ```typescript interface BackoffConfig { maxRetries: number; baseDelayMs: number; ...