Skip to main content
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:
Where each component has a specific role:

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
Each endpoint documents its required and optional parameters individually.