Skip to main content
POST
Verify one email address.
This page renders the machine-readable request, response, and status-code contract from openapi.yaml. Use it to inspect field shapes; use the single-verification guide for the operational workflow. The specification models canonical X-Api-Key authentication and HTTP Bearer compatibility for existing integrations; new code should use X-Api-Key. The source does not prefill a credential. Hosted-playground storage behavior requires a separate browser verification before launch, so use the curl quickstart with a controlled key until that check is complete. HTTP 200 includes the completed Pre-Send decision and engine metadata. HTTP 202 represents accepted or still-running work, carries no decision, and has no public single-result polling route in the four-route GA contract. Treat those response shapes separately in generated clients.

Authorizations

X-Api-Key
string
header
required

Canonical authentication. Send a Bounceless key in blc.… format.

Headers

Idempotency-Key
string
required
Minimum string length: 1

Body

application/json
email
string<email>
required
Maximum string length: 320
timeoutMs
integer
Required range: 1 <= x <= 120000

Response

Completed

status
enum<string>
required
Available options:
completed,
queued,
running
presend
object
required
requestId
string
required
decision
object | null
engine
object

Present on a completed 200 response and absent while a 202 response is still accepted or running.

engineJobId
string

Present on a 202 accepted response. No public single-result polling route is defined by this contract.