When the API request is sent to the TLC server, a response is triggered with an http status code. Status codes are available for successful requests and failure requests. For each failure request, you get a response with an API error code indicating the reason for the failure. The following table displays the list of API error codes and the corresponding http status code for each API error code.
Error code | Description | Http Status code |
|---|---|---|
1 | One or more mandatory parameters are empty. | 400 |
2 | One or more parameters have invalid value. | 400 |
3 | Internal system error. | 500 |
4 | API is not initialized. | 500 |
5 | API request is made to a domain which is not monitored. | 406 |
6 | API request is made to a passive Logon Collector server. | 406 |
7 | User is created in the domain but has not logged in the domain. | 400 |
8 | The data is sent to the TLC server in an invalid JSON format. | 400 |
Status codes
The following table lists the http status codes:
Http Status code | Description | API request (success/failure) |
|---|---|---|
200 | The requested data is found in TLC server | success |
201 | Create operation is successfully done in the TLC server | success |
202 | When a user exists in AD but does not exist in TLC and if Login API is requested for this user, a pending logon will be created in TLC and it will be processed asynchronously in TLC. | pending |
204 | Delete operation is successfully done in the TLC server | success |
401 | Request is not authorized due to any of the following reasons:
| failure |
400 | The server cannot understand the request due to malformed syntax | failure |
404 | The server has not found anything matching the request | failure |
406 | The identified resource can only generate response entities that has only the content characteristics that is not acceptable to the accept headers sent in the request. | failure |
500 | The server encountered an unexpected condition which prevented it from fulfilling the request | failure |