# Understanding HTTP Status Codes

When you send an API request to the server, the server returns a response along with the status codes. The status code helps you understand whether the request was successful or any error occurred. 

The following are the most commonly used HTTP Status Codes along with their descriptions: 

<table data-header-hidden><thead><tr><th width="180"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Status Code</strong> </td><td><strong>Result</strong></td><td><strong>Description</strong> </td></tr><tr><td>200 OK </td><td>Success </td><td>The request was successful, and the server returned the expected response. </td></tr><tr><td>201 Created </td><td>Resource Created </td><td>The request was successful, and a new resource was created on the server. </td></tr><tr><td>204 No Content </td><td>Success (No Data) </td><td>The request was successful, but the server did not return any content. </td></tr><tr><td>400 Bad Request </td><td>Invalid Request </td><td>The server could not understand the request due to invalid syntax or missing information. </td></tr><tr><td>401 Unauthorized </td><td>Authentication Failed </td><td>Authentication is required or provided credentials are invalid. </td></tr><tr><td>403 Forbidden </td><td>Access Denied </td><td>The user does not have permission to access the requested resource. </td></tr><tr><td>404 Not Found </td><td>Resource Not Found </td><td>The requested resource or endpoint could not be found on the server. </td></tr><tr><td>405 Method Not Allowed </td><td>Invalid Method </td><td>The request HTTP method (GET, POST, etc.) is not supported for the requested resource. </td></tr><tr><td>408 Request Timeout </td><td>Timeout </td><td>The request took too long, and the server stopped waiting for a response. </td></tr><tr><td>409 Conflict </td><td>Request Conflict </td><td>The request could not be completed due to a conflict with the current server state. </td></tr><tr><td>415 Unsupported Media Type </td><td>Invalid Content Type </td><td>The server cannot process the request because of an unsupported format in the body or headers. </td></tr><tr><td>429 Too Many Requests </td><td>Rate Limit Exceeded </td><td>The client has sent too many requests in a short period of time. </td></tr><tr><td>500 Internal Server Error </td><td>Server Error </td><td>The server encountered an unexpected condition that prevented it from fulfilling the request. </td></tr><tr><td>502 Bad Gateway </td><td>Gateway Error </td><td>The server received an invalid response from another server while processing the request. </td></tr><tr><td>503 Service Unavailable </td><td>Server Unavailable </td><td>The server is currently unavailable due to maintenance or overload. </td></tr><tr><td>504 Gateway Timeout </td><td>Timeout </td><td>The server did not receive a timely response from another server. </td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/avo-assure-supported-technologies-for-automation/webservice-automation/understanding-http-status-codes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.