> ## Documentation Index
> Fetch the complete documentation index at: https://developers.debounce.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Responses

> Format and structure of DeBounce API responses

DeBounce API responses follow a consistent structure.\
Each response includes a `success` field that indicates whether the request was processed successfully.

* `success = "1"` → the request was successful
* `success = "0"` → the request failed, and an error message may be included

When a request succeeds, the main data is returned inside the `debounce` object.\
When a request fails, the `debounce` object contains error details.

## Success Response

A typical successful response includes:

* The validated email address
* A result status such as Safe to Send, Invalid, Disposable, etc.
* Metadata fields (role account, free email, did-you-mean suggestions, etc.)
* Remaining balance

Example:

```json theme={null}
HTTP/1.1 200 OK

{
  "debounce": {
    "email": "mohsen@gmail.com",
    "code": "5",
    "role": "false",
    "free_email": "true",
    "result": "Safe to Send",
    "reason": "Deliverable",
    "send_transactional": "1",
    "did_you_mean": ""
  },
  "success": "1",
  "balance": "1725935"
}
```

## Error Response

When an error occurs, the `debounce` object contains information about the failure.\
Common reasons include invalid API keys, missing parameters, or malformed requests.

Example:

```json theme={null}
HTTP/1.1 401 Unauthorized

{
  "debounce": {
    "error": "Wrong API",
    "code": "0"
  },
  "success": "0"
}
```

## Notes

<Note>
  Each endpoint documents its own additional fields, result codes, and metadata. Use this page as a general reference for the overall response structure.
</Note>