# Response Codes

The API mostly uses conventional HTTP response codes to indicate the success or failure of an API request.

**General Status Code Meaning**

<table data-view="cards"><thead><tr><th>Code Range</th><th>Status</th></tr></thead><tbody><tr><td>200-299</td><td>Success</td></tr><tr><td>400-499</td><td>Error with the information provided</td></tr><tr><td>500+</td><td>Error with Ping Proxies Servers</td></tr></tbody></table>

**Specific Success Code Meaning**

| Code | Status                                                             |
| ---- | ------------------------------------------------------------------ |
| 200  | The request was completed successfully.                            |
| 201  | The request was completed successfully and a resource was created. |

**Specific Error Code Meaning**

<table><thead><tr><th>Code</th><th>Status</th><th data-type="rating" data-max="5">Occurence</th></tr></thead><tbody><tr><td>400</td><td>The information sent in the request was malformed or did not pass validation.</td><td>5</td></tr><tr><td>401</td><td>The request requires authorization which was not provided.</td><td>3</td></tr><tr><td>403</td><td>The request has authorization but the attempted operation was specifically forbidden by the server.</td><td>1</td></tr><tr><td>404</td><td>The specific resource requested in the request was not found.</td><td>3</td></tr><tr><td>405</td><td>The method of the request was not supported.</td><td>1</td></tr><tr><td>409</td><td>The information provided in the request conflicts with another resource.</td><td>2</td></tr><tr><td>422</td><td>The request is unprocessable as the information and operation fail to comply with internal business logic.</td><td>5</td></tr><tr><td>429</td><td>The user has exceeded the rate limit for the requested operation or resource.</td><td>3</td></tr><tr><td>499</td><td>The request requires two-factor authentication. Please retry the request with two-factor authentication details appended.</td><td>3</td></tr><tr><td>500</td><td>An unexpected error occurred on the Ping Proxies server.</td><td>1</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://internal.developer.documentation.private.user.pingproxies.com/basic-concepts/getting-started/response-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.