miro-common-errors

# Miro Common Errors ## Overview Quick reference for Miro REST API v2 errors organized by HTTP status code, with real error response bodies and proven fixes. ## Prerequisites - Access token configured - `curl` available for diagnostic requests ## Quick Diagnostic ```bash # 1. Verify API connectivity curl -s -o /dev/null -w "%{http_code}" https://api.miro.com/v2/boards \ -H "Authorization: Bearer $MIRO_ACCESS_TOKEN" # 2. Check token validity curl -s https://api.miro.com/v1/oauth-token \ -H "Authorization: Bearer $MIRO_ACCESS_TOKEN" | jq # 3. Check Miro status page curl -s https://status.miro.com/api/v2/status.json | jq '.status.description' ``` ## Error Reference ### 400 — Bad Request ```json { "status": 400, "code": "invalidInput", "message": "Could not resolve the value for parameter: data.content", "context": { "fields": [{ "field": "data.content", "message": "Required" }] } } ``` **Common causes:** - Missing required fields in request body - Wrong data types (string instead of number for position) - Invalid enum values (e.g., `shape: 'oval'` — correct is `shape: 'circle'`) **Fix:** Cross-reference your request body with the [REST API reference](https://developers.miro.com/docs/rest-api-reference-guide). Each item type has specific required fields. **Sticky note required fields:** `data.content`, `data.shape` (`square` or `rectangle`) **Shape required fields:** `data.shape` (see `miro-sdk-patterns` for valid shapes) **Connector required fields:** `...