This section is to help developers with solutions to the REST API response codes.
General Error Codes
Response Code |
Meaning |
Description |
---|---|---|
301 |
Permanent Location |
The requested resource resides on a URI other than the requested one.You need to set up the authentication type to access the API. |
400 |
Bad Request |
The requested operation cannot be executed because the service cannot understand the data sent in the entity body of the request. |
401 |
Unauthorized |
The client is not authenticated. |
403 |
Forbidden |
Access to the resource is denied. |
404 |
Not Found |
The requested resource cannot be found. |
405 |
Method Not Allowed |
The requested method is not supported for the given resource. |
406 |
Not Acceptable |
You need to set up the authentication type to access the API.The requested method does not produce any of the media types requested in the HTTP request. |
409 |
Conflict |
The operation cannot be completed because it conflicts with an existing resource. |
415 |
Unsupported Media Type |
The REST service does not support the API version requested by the REST client. |
500 |
Internal Server Error |
The operation cannot be completed due to a service error. |
503 |
|
The service is currently unavailable. |
In addition to the general error codes, the REST APIs return one of the following detailed error codes as an X-message-code HTTP response header:
Detailed Error Codes
REST API |
X-message code |
Description |
---|---|---|
Invitation REST API |
INVITATION_API_PARAMETER_INCORRECT |
You have used an invalid parameter. |
INVITATION_API_EMAIL_INCORRECT |
You have specified an incorrect address or the email address does not exist. |
|
PASSWORD_LOCKED |
The password is locked for 60 minutes after 5 failed logon attempts with wrong value. |
|
User Management REST API |
PASSWORD_LOCKED |
The password is locked for 60 minutes after 5 failed logon attempts with wrong value. |
Update Group Resource SCIM REST API |
Mismatched group id |
The |
Response Code |
Meaning |
Description |
---|---|---|
200 |
OK |
Operation successful. |
201 |
Created |
Entity created successfully. |
204 |
No Content |
The service received and understood the request, but there is no need to send any content back. |
Check also the troubleshooting scenarios available in the Guided Answers tool.
See Guided Answers.
Related Information