Status Codes
Upon receiving a request, the TPM Data Service returns a response containing one of the following standard HTTP status codes.
HTTP Status Code | Description |
|---|---|
200 OK | Request completed successfully. A 200 status is returned when a request is successfully processed. The 200 status response is also returned in special cases like below : - When the user requested for the data, if the request is still being processed then status code :- 200 response :- {"data":{"STATUS": "Processing"}} When the user requested for the data, if the data is being cleared in the server cache tables then status code :- 200 response :- {"data":{"STATUS": "NO DATA (The Results Are Cleaned Up)"}} When the user requested for the data, if the request is failed while due to data errors. status code :- 200 response :- {"data":{"STATUS": "FAILED"}}
|
400 Bad Request | The request could not be processed because it is missing information, contains invalid information, or has syntax errors. The 400 status response is also returned in special cases like below : - When user 'A' is requested the data (gets the key in response ), and user 'B' is trying to access the data then the response message will be like status code :- 400 response : - 'B' : user can not access the data. When the user requested for the data with invalid key(key which is not created by the server). status code : 400 response :- No Record Found For Given Key with User : 'A'
|
404 Not Found | The request includes a URI that does not exist. |
401 Unauthorized | The request is not authorized. The authentication credentials included with this request are missing or invalid.
|
403 Forbidden | The user cannot be authenticated. The user does not have authorization to perform this request.
|
405 Method Not Allowed | The HTTP verb specified in the request ( ) is not supported for this request URI. |
406 Not Acceptable
| The object identified by this request is not capable of generating a representation corresponding to one of the media types in the Accept header of the request. For example, the client's Accept request header may require XML format return values, but the data service may only return JSON format values |
415 Not Acceptable | The client's ContentType header is not correct. For example, the client attempts to send the request in XML, but the resource can only accept JSON. |
500 Internal Server Error | The server encountered an unexpected error that prevented it from fulfilling the request. |
503 Service Unavailable | The server is unable to handle the request due to temporary overloading or maintenance. |
Last Published Tuesday, February 6, 2024