The Email Validation API offers a set of endpoints for validating single emails, processing bulk lists, tracking job progress, downloading results, and managing credits.
This overview provides a high-level summary of each endpoint category and links to their dedicated pages.

1. Single Email Validation

POST /api/validate

Validate one email address in real time.

Use this endpoint when:

• Validating emails during signup

• Cleaning small datasets

• Checking a single address before sending mail

Key Capabilities

• Syntax check

• Domain & MX lookup

• SMTP mailbox verification

• Disposable, role-based, spamtrap, abuse detection

• Scoring (0–100)

Response Includes

• status (VALID, INVALID, DO_NOT_MAIL, etc.)

• score

• Risk flags

• MX & SMTP details

👉 See full details in: Single Email Validation section

2. Bulk Validation (Jobs API)

Process thousands of emails asynchronously via jobs.
Bulk endpoints support raw lists, CSV upload, JSON upload, and text files.

2.1 Create a Job

POST /api/v1/jobs

Submit an array of email addresses.

2.2 Upload a File

POST /api/v1/jobs/upload

Upload CSV / JSON / TXT file (up to 10 MB).

File-based jobs are recommended for:

• CRM list validation

• Marketing lists

• Large exports

2.3 Check Job Status

GET /api/v1/jobs/{job_id}/status

Returns:

• Total emails

• Processed count

• Valid/invalid counts

• Progress percentage

• Job timestamps

Status values:

• queued

• processing

• completed

• failed

2.4 Fetch Processed Results

GET /api/v1/jobs/{job_id}/results

Returns paginated JSON results.

Query parameters:

• page

• limit

• format=csv|json

2.5 Download Full Results File

GET /api/v1/jobs/{job_id}/download`

Download CSV or JSON output.

Results available for 7 days before automatic deletion.

👉 See full details in: Bulk Validation section

3. Realtime Progress (SSE)

GET /api/v1/jobs/{job_id}/stream

Receive live updates while a job is processing.

Event Types

• status — includes progress percentage

• error — job failure

Useful for:

• Dashboard progress bars

• Admin consoles

• Background job monitoring

👉 See full details in: Realtime SSE section

4. Credits & Billing API

Manage or monitor your API credit usage (pay-as-you-go or subscription).

4.1 Credit Balance

GET /api/v1/credits/balance

Returns:

• Available credits

• Used credits

• Subscription credits

• Bonus credits

• Reserved credits

Error when out of credits:

{
  "error": {
    "code": "INSUFFICIENT_CREDITS"
  }
}

👉 See full details in: Credits & Billing section

5. Error Handling & Status Codes

All endpoints follow a consistent error format.

Common status codes:

• 200 — Success

• 202 — Accepted (bulk job created)

• 400 — Invalid request

• 401 — Invalid/missing API key

• 402 — Not enough credits

• 403 — Forbidden

• 404 — Resource not found

• 410 — Job results expired

• 413 — File too large

• 429 — Rate limit exceeded

• 500 — Server error

👉 See full details in: Errors & Status Codes section

6. Field Schema

Every email validation includes a rich set of metadata fields.
Developers often need a reference to:

• status values

• score meaning

• validations.* booleans

• is_spamtrap, is_abuse, is_toxic

• MX / SMTP fields

• Domain & provider info

👉 See full details in: Field-Level Schema section

Summary Table