General Response Code for Log Server API
This table outlines the standard HTTP response codes used by the Log Server’s API to communicate the result of client requests. These codes help clients understand whether their requests were successful or if errors occurred, and what kind of errors were encountered. Understanding these response codes is crucial for diagnosing issues, debugging API calls, and ensuring smooth integration with the Log Server.
| Error | Status | Description |
|---|---|---|
| 200 | OK | The request was successful. |
| 400 | Bad request. | The server could not process the request due to missing parameters, malformed syntax, or absence of required HTTP headers. For example, if fields like MachineName or Role are missing in the request headers, this response is triggered. |
| 401 | Not Authorized. | The request was denied because the client is not authorized. This usually occurs when the IP address or the authentication key (AuthKey) used is not permitted to access the Log Server. |
| 404 | Not found. | The API path requested does not exist. This response is returned when the endpoint is invalid or mistyped. |
| 500 | Internal error. | Indicates that the Log Server encountered an unexpected condition preventing it from fulfilling the request. This is commonly caused by server-side issues such as resource exhaustion (e.g., memory or disk space). |
General Response Code for Log Server API
In this article
Copied!
Failed!