> ## 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.

# Requests – URL Formats

> Understanding DeBounce API request structure and parameters

DeBounce API requests follow a simple URL-based structure.\
Each endpoint uses query parameters to define what data you want to validate or retrieve.

## General URL Structure

Most requests follow this format:

```
https://{hostname}/{path}?{parameters}
```

Where each component has a specific role:

| Component | Description |
| - | - |
| **hostname** | The service domain handling the request, such as `api.debounce.io`, `bulk.debounce.io`, or `disposable.debounce.io`. |
| **path** | The specific API route being called, such as `single`, `bulk/status`, or `free/disposable`. |
| **parameters** | Query parameters that define the request, such as the email address, API key, or file token. |

## How DeBounce Uses URL Parameters

DeBounce endpoints rely on simple query-string parameters.\
Common examples include:

* `api` — your API key
* `email` — email address to validate
* `task_id` — reference to a bulk validation job
* `file` — file token used for retrieving bulk results

<Note>
  Each endpoint documents its required and optional parameters individually.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.