Errors
An error response may occur on invalid requests e.g. on missing parameters, unknown resources or unauthorized access.
The MindMeister API uses standard HTTP status codes and custom error objects to provide a machine-readable and user friendly response.
HTTP Status Codes
Status | Description |
---|---|
2xx | The request was successfully received, understood, and accepted. |
3xx | Further action is needed to fulfill the request. |
4xx | The client sent an invalid request. In most cases some parameters are missing or incorrect. |
5xx | An error occured on the server and is incapable of performing the request. |
Error Response Object
The error response JSON object is always in the following format and sent in the response body.
{
"error": {
"type": "errorType",
"message": "Error message",
"details": "OPTIONAL error details"
}
}
Error Types
Error Type | Status | Description |
---|---|---|
internalServerError | 500 | An internal server error occured. Please submit a request to get this fixed soon. |
notFound | 404 | The requested resource is not found. |
notAcceptable | 406 | The requested resource is not available due to the Accept header format. |
unprocessableEntity | 422 | The request resource couldn't be processed due to semantic errors. |
forbidden | 403 | The request was refused due to insufficient permissions. |
invalidCredentials | 401 | The request was refused because authentication failed. |
unauthorizedScopes | 403 | The provided scopes are insufficient. |
productUnknown | 400 | The product parameter is missing or unknown. |
userInvalid | 400 | The user resource is invalid due to semantic errors. |
accessTokenInvalid | 400 | The access token is invalid due to semantic errors. |
resourceInvalid | 400 | The requested resource is invalid due to semantic errors. |
Updated less than a minute ago