# Errors

Our API uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the `2xx` range indicate success. Codes in the `4xx` range indicate an error that failed given the information provided (e.g., a required parameter was omitted, a charge failed, etc.). Codes in the `5xx` range indicate an error with our servers (these are rare).

Some `4xx` errors that could be handled programmatically include an error code that briefly explains the error reported.

## Error code

Attributes are returned as JSON objects, examplified as follows:

```json
{
    "title": "",
    "type" : "",
    "traceId" : ""
}
```

### Attributes

**title** (string)\
A human-readable message providing more details about the error. 

**traceId** (string)\
A traceable id which corrolates with our logging records.

**type** (string)\
The type of error returned.


---

# 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://devs.debitdirect.io/getting-started/errors.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.