DeBounce API requests follow a simple URL-based structure.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.
Each endpoint uses query parameters to define what data you want to validate or retrieve.
General URL Structure
Most requests follow this format:| 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 keyemail— email address to validatetask_id— reference to a bulk validation jobfile— file token used for retrieving bulk results
Each endpoint documents its required and optional parameters individually.