deepVerification flag, and Clodura responds immediately with a result if verification completes quickly (200 OK), or queues an asynchronous job and returns a 202 Accepted when the domain requires deeper analysis — such as catch-all domains or high-security mail servers. Once a queued job finishes, Clodura posts the final verdict to your webhookUrl.
Standard verification is fast and suitable for most business email addresses. Deep verification takes longer but is the right choice for validating catch-all domains where a standard check cannot determine true deliverability.
Credit cost:
- Standard verification: 0.04 credits per request
- Deep verification: 0.1 credits per request
Plan availability: This endpoint is available on Free Forever, Max, and PAYG plans. If you are on an Enterprise or legacy plan not listed, contact support@clodura.ai to discuss access.
Endpoint
POST /api/v1/verify/email
Request
Headers
| Header | Value |
|---|---|
X-API-KEY | Your Clodura API key |
Content-Type | application/json |
Body Parameters
The email address you want to verify (e.g.,
john@example.com).When
true, Clodura performs deep verification suitable for catch-all domains and high-security mail servers. Costs 0.1 credits. When false (default), standard verification is used at 0.04 credits.The URL where Clodura will POST the final verification result once processing completes. Strongly recommended for deep verification, where results may not be immediate.
Example Request
Response
200 OK — Synchronous Result
Returned when verification completes immediately. The email’s deliverability verdict is available in the response body.The email address that was verified.
Indicates whether deep verification was used for this request.
A unique document ID for this verification job. Use this to poll for results or match incoming webhook payloads.
Current processing state:
In-progress or Completed.The deliverability verdict:
Deliverable, Undeliverable, Risky (Catch-all), or Pending.ISO 8601 timestamp indicating when the verification job was created.
202 Accepted — Asynchronous Job Queued
Returned when the verification requires more time — typically for deep verification or catch-all domains. The result is delivered to yourwebhookUrl once processing finishes.
The email address submitted for verification.
Indicates whether deep verification was requested.
A unique identifier for this job. Match this against incoming webhook payloads.
Current state:
In-progress.Current status:
Pending until the job completes.ISO 8601 timestamp of job creation.
Always
true for 202 responses, confirming the job is queued.Webhook Payload Schema
Once verification finishes, Clodura POSTs the following payload to yourwebhookUrl:
| Field | Type | Description |
|---|---|---|
email | string | The verified email address |
deepVerification | boolean | true if deep verification was used |
trackingId | string | Document ID — matches the ID in the initial response |
verificationProgress | string | In-progress or Completed |
verificationStatus | string | Deliverable, Undeliverable, Risky (Catch-all), or Pending |
createdAt | string | ISO 8601 timestamp of job creation |
Verification Status Values
| Status | Meaning |
|---|---|
Deliverable | The email address is valid and messages will be accepted. |
Undeliverable | The email address does not exist or will permanently reject mail. |
Risky (Catch-all) | The domain accepts all email regardless of whether the mailbox exists — deliverability cannot be confirmed. |
Pending | Verification is still in progress (only seen in 202 responses). |
Error Codes
| Status | Meaning |
|---|---|
400 | Bad request — email format is invalid |
402 | Payment required — credits exhausted; upgrade your plan or add credits |
403 | Forbidden — email verification is not available on your current plan |
500 | Internal server error — an unexpected error occurred |
