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
Error response examples:

{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:Error"
    ],
    "status": "404",
    "detail": "No valid resources: [{memberId=3074457345618258730, display=null}, {memberId=4567543256789076, display=null}]"
}
{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:Error"
    ],
    "status": "409",
    "detail": "[email protected] is not whitelisted"
}
{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:Error"
    ],
    "status": "400",
    "scimType": "invalidValue",
    "detail": "User name '[email protected]' is invalid: 'not unique'"
}
{
    "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:

Status

Description

400

Bad Request.

Unexpected request. The "detail" attribute of resource should provide information on what request/attribute value is unexpected.

401

Unauthorized.

Miro cannot authorize organization by authorization token

403

Forbidden.

SCIM integration is disabled.

404

Not Found.

Requested resource not found by id

405

Method not allowed.

Miro doesn't support the requested method.

409

Conflict.

Miro cannot update a resource because of logic conflict.

413

Payload too large.

The payload is bigger than the maximum payload amount of 800000 bytes.

415

Unsupported Media Type.

The media type that you provide is unsupported by this endpoint.

429

Too many requests.

The request is rejected by rate limits.

500

Internal Server Error.

An unexpected error of application. Please, contact Miro support to clarify the reason for such an error.


Did this page help you?