---
updatedAt: 2026-03-19T19:40:03.000Z
agentTools:
  projectIndex: https://developers.miro.com/llms.txt
---

# Errors

Interacting with our APIs may result in an error instead of the expecting result. Miro tries to respond with a detailed error message that will help you figure out what went wrong and how to fix it.

[SCIM error schema](https://www.rfc-editor.org/rfc/rfc7644.html#section-3.12)\
Error response examples:

```json 404 error response example
{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:Error"
    ],
    "status": "404",
    "detail": "No valid resources: [{memberId=3074457345618258730, display=null}, {memberId=4567543256789076, display=null}]"
}
```
```json 409 error response example
{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:Error"
    ],
    "status": "409",
    "detail": "userEmail@test.com is not whitelisted"
}
```
```json 400 error response example
{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:Error"
    ],
    "status": "400",
    "scimType": "invalidValue",
    "detail": "User name 'userEmail@test.com' is invalid: 'not unique'"
}
```
```json 429 error response example
{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:Error"
    ],
    "status": "429",
    "scimType": "tooManyRequests",
    "detail": "The user has sent too many requests in a given amount of time"
}
```

Possible errors:

[block:parameters]
{
  "data": {
    "h-0": "Status",
    "h-1": "Description",
    "0-0": "400",
    "0-1": "Bad Request.  \n  \nUnexpected request.  \nThe `detail` attribute of the resource should provide information on what request/attribute value is unexpected.",
    "1-0": "401",
    "1-1": "Unauthorized.  \n  \nMiro cannot authorize the organization with the authorization token.",
    "2-0": "403",
    "2-1": "Forbidden.  \n  \nSCIM integration is disabled.",
    "3-0": "404",
    "3-1": "Not Found.  \n  \nThe requested resource wasn't found by looking up its ID.",
    "4-0": "405",
    "4-1": "Method not allowed.  \n  \nMiro doesn't support the requested method.",
    "5-0": "409",
    "5-1": "Conflict.  \n  \nMiro cannot update a resource because of a business logic conflict.  \nThe logic conflict can vary, depending on the real-life scenario.  \nFor example:  \n  \n-  Try to allow an email address that isn't included in the allow list (whitelist).  \n- Try to add or update the email address of a user whose status is inactive.  \n- Try to update the details of a user who belongs to more than one organization.  \n- Try to update the details of an enterprise user who exists in Miro as an _uncaptured user_: the user profile exists in Miro, but the profile isn't a member of a team within the enterprise; therefore, enterprise admins cannot retrieve it.",
    "6-0": "413",
    "6-1": "Payload too large.  \n  \nThe payload exceeds the maximum payload of 800000 bytes.",
    "7-0": "415",
    "7-1": "Unsupported Media Type.  \n  \nThe endpoint doesn't support the provided media type.",
    "8-0": "429",
    "8-1": "Too many requests.  \n  \nThe request is rejected by [rate limits](https://developers.miro.com/docs/scim-rate-limits).",
    "9-0": "500",
    "9-1": "Internal Server Error.  \n  \nAn unexpected error of application.  \nPlease, contact Miro support to clarify the reason for such an error."
  },
  "cols": 2,
  "rows": 10,
  "align": [
    "left",
    "left"
  ]
}
[/block]