# Error Handling

Our API communicates errors through standard HTTP status codes and provides detailed error messages in the response body. Here are common HTTP status codes and their meanings:

### Common HTTP Status Codes

* **200 OK:** The request was successful.
* **400 Bad Request:** The request was malformed or invalid.
* **401 Unauthorized:** Authentication failed or missing credentials.
* **404 Not Found:** The requested resource was not found.
* **429 Too Many Requests:** Exceeded rate limits.

### Handling Errors

When an error occurs, the API response includes a JSON object with an `error` field containing the error message. Example:

```json
{
  "error": "Invalid API key. Please provide a valid key."
}
```


---

# 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://developer.providusbank.com/reference/api-reference/error-handling.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.