Status Codes
Upon receiving a request, TPM API returns a response containing one of the following standard HTTPS status codes.
HTTPS Status Code | Brief Description | Description |
200 | OK | Request completed successfully. A 200 status is returned when a request is successfully processed. |
201 | Created | Job has been created. |
202 | Accepted | Job still executing. |
400 | Bad Request | The request could not be processed because it is missing information, contains invalid information, or has syntax errors. |
404 | Not Found | The request includes a URI that does not exist. |
401 | Unauthorized | The request is not authorized. The user does not have authorization to perform this request. |
403 | Forbidden | The user cannot be authenticated. The user credentials included with this request are invalid, the user's password has expired or the user account has been locked. |
405 | Method Not Allowed | The HTTPS verb specified in the request (POST, GET, etc.) is not supported for this 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. |
413 | Request Entity Too Large | The request is larger than the server is able to handle. |
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. |
502 | Bad Gateway Error | The server is unable to handle the request due to temporary system maintenance or overload. |
503 | Service Unavailable | The server is unable to handle the request due to temporary overloading or maintenance. |