Errors
When interacting with the API, various errors may occur due to issues with the request or server.
Identity360 APIs return errors in a consistent format to help you understand and troubleshoot issues. The error response includes an error code, a detailed message, and a title that describes the error type.
{
"error": {
"code": <error code>
"detail": <error message>
"title": <title>
}
}
ID360 API Error Codes
When using the Identity360 API, you may encounter various error codes that indicate specific issues encountered during the request process. These error codes are designed to provide clear and concise information about the nature of the problem, allowing you to take appropriate action to resolve it.
Error Code | Title | Description |
---|---|---|
Client Errors | ||
00000100 | Bad Request | The server could not process the request due to a client error, such as malformed request syntax, invalid message framing, or misleading request routing. |
00000101 | Unauthorized | An invalid OAuth token was sent. |
00000102 | Unprocessable Content | The request was well-formed but was unable to be followed due to semantic errors. |
00000103 | Unsupported Media Type | The media format of the requested data is not supported by the server, so the server is rejecting the request. |
00000104 | Page Not Found | A request was made to an unsupported endpoint. |
00000105 | Unsupported HTTP Method | An unsupported HTTP method was used to request an endpoint. |
00000106 | Forbidden | The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server. |
00000107 | Invalid Parameter | An input parameter is invalid or not acceptable for the operation being performed. |
00000108 | Content Length is Required | The server rejected the request because the Content-Length header field is not defined and the server requires it. |
00000109 | Too Many Requests | The server rejected the request because the Content-Length header field is not defined and the server requires it. |
00010104 | Invalid Attribute Found | The provided select or sort attribute has invalid attribute(s). |
00010105 | User Not Found | The specified user in the request was not found, or the user attempting to perform the action lacks the necessary permissions to do so. |
00010106 | Directory Not found | The directory ID provided in the request is invalid or does not match any existing directories. |
00010109 | Unlicensed User | The provided user ID is associated with an unlicensed user, and actions cannot be performed on users without a valid license. |
00010110 | Invalid Attribute Value | The value provided for an attribute is invalid. For example, if the API expects the country to be in the ISO 3166-1 code format, but the user inputs India or an incorrect code, it is considered an invalid value for the country attribute. |
00010111 | Template Validation Failed | This error occurs during template validation when creating a user. It indicates that there is an issue with the input. |
00010112 | Template Not Found | The provided template ID is invalid or not applicable for the current directory. The template ID cannot be null—it must correspond to the directory where the action is being performed, and currently, only templates for Zoho are supported. Additionally, templates with multiple mandatory directories are not supported at this time. |
00010113 | Invalid Pagination Cursor | The pagination cursor provided is invalid. It either has an incorrect format or does not align with the one generated by the system. |
09000001 | Invalid Input Data. | The input data provided in the request is either missing, incomplete, or does not meet the required format. |
Serve Errors | ||
00010108 | API Action Timeout | This error occurs if the request takes longer than two minutes to process. In the future, a follow-up link will be provided to allow you to check the status of the request later. |
00000000 | Internal Server Error | An unexpected internal error has occurred on the server. Please try again later. |