Email Verifier API website screenshot

Email Verifier API

Email Verifier API is a real-time email verification service offering a 16-point engine that validates deliverability through syntax checking, DNS / MX lookups, real-time SMTP handshakes, mailbox existence probing, catch-all and greylisting detection, disposable address detection, role-account flagging, spam-trap and complainer detection, gibberish and offensive-language scanning, B2B / B2C classification, typo correction, and SMTP provider identification. The service is delivered as a single REST endpoint that accepts GET or POST requests, returns JSON or XML, and meters usage against a credit-pack balance that never expires. The product targets growth teams, ESPs, and lead-generation operators that need to eliminate hard bounces and protect sender reputation before they send.

1 APIs 12 Features
Email VerificationDeliverabilitySMTP CheckBounce PreventionLead ValidationDisposable DetectionSpam Trap DetectionCatch-All DetectionGreylistingRole Account DetectionTypo SuggestionB2B Lead Scoring

APIs

Email Verifier API Verification

Real-time email-address verification endpoint. Single resource at https://emailverifierapi.com/v2/ accepting GET or POST. Returns a top-level deliverability status (passed / fai...

Collections

Email Verifier API

OPEN

Pricing Plans

Email Verifier Api Plans Pricing

14 plans

PLANS

Rate Limits

Email Verifier Api Rate Limits

3 limits

RATE LIMITS

FinOps

Email Verifier Api Finops

FINOPS

Features

16-Point Verification Engine

Composite engine combining syntax, DNS, MX, SMTP handshake, mailbox existence, catch-all, greylisting, disposable, role, spam-trap, gibberish, offensive, B2B, typo, complainer, and SMTP-provider checks.

Real-Time SMTP Verification

Live RCPT TO probe against the destination MX to confirm mailbox existence in real time.

Disposable Detection

Match against 50,000+ known disposable / burner email providers.

Role-Account Detection

Flag departmental aliases such as info@, sales@, support@, marketing@.

Catch-All Detection

Identify domains whose MX accepts all addresses regardless of mailbox existence.

Greylisting Handling

Distinguish temporary SMTP defenses from outright rejections so they can be retried.

Typo Suggestion

Detect domain misspellings (gmial.com -> gmail.com) and return a corrected address.

Spam-Trap and Complainer Detection

Identify honeypots and chronic spam-complainer addresses before they damage sender reputation.

B2B / B2C Classification

Classify addresses as corporate (B2B) versus consumer (B2C) free-mailbox providers.

Credit-Based Metering

Pay-as-you-go credit packs that never expire; only Paid (mailbox-level) events consume credits.

JSON or XML Response

JSON by default; XML available with `xml=true`.

GET or POST

Both GET and POST supported on the single endpoint for ad-hoc and server-to-server use.

Use Cases

Signup Validation

Block disposable, role, and invalid addresses at registration to keep user lists clean.

Pre-Send List Cleaning

Run marketing lists through verification before a send to lower bounce rate and protect IP / domain reputation.

Lead Quality Scoring

Score inbound leads on B2B vs B2C, role-account, and disposable signals to prioritize sales follow-up.

ESP Bounce Prevention

Reduce hard bounces on transactional and marketing sends to maintain ISP reputation.

Typo Recovery at Form Submit

Use `emailSuggested` to prompt users with the corrected address inline at signup.

Integrations

Salesforce

Apex HTTP-callout integration for lead validation inside Salesforce.

Google Sheets

Spreadsheet workflow for ad-hoc list verification.

Microsoft Excel

Spreadsheet workflow for ad-hoc list verification.

HubSpot

Marketing-platform integration for list cleansing.

Pipedrive

CRM integration for inbound lead validation.

Semantic Vocabularies

Email Verifier Api Context

18 classes · 3 properties

JSON-LD

API Governance Rules

Email Verifier API API Rules

9 rules · 6 errors 3 warnings

SPECTRAL

JSON Structure

Email Verifier Api Verification Result Structure

18 properties

JSON STRUCTURE

Example Payloads

Email Verifier Api Disposable Example

18 fields

EXAMPLE

Email Verifier Api Mailbox Does Not Exist Example

18 fields

EXAMPLE

Email Verifier Api Mailbox Exists Example

18 fields

EXAMPLE

Email Verifier Api Typo Suggest Example

18 fields

EXAMPLE

Resources

🔗
Documentation
Documentation
📝
Signup
Signup
🔗
Login
Login
💰
Pricing
Pricing
📰
Blog
Blog
📜
TermsOfService
TermsOfService
📜
PrivacyPolicy
PrivacyPolicy
🔧
FreeTool
FreeTool
🔗
Directory
Directory
💬
Support
Support
🔗
LlmsText
LlmsText

Sources

Raw ↑ 
opencollection: 1.0.0
info:
  name: Email Verifier API
  version: '2.0'
request:
  auth:
    type: apikey
    key: apiKey
    value: '{{apiKey}}'
    placement: query
items:
- info:
    name: Verification
    type: folder
  items:
  - info:
      name: Verify Email Address
      type: http
    http:
      method: GET
      url: https://emailverifierapi.com/v2/
      params:
      - name: apiKey
        value: ''
        type: query
        description: Customer API key.
      - name: email
        value: ''
        type: query
        description: Email address to verify.
      - name: xml
        value: ''
        type: query
        description: Set to `true` to receive an XML response payload instead of JSON.
    docs: 'Run the 16-point verification engine against a single email address and return a

      deliverability verdict (`status`), a granular event code (`event`), a human-readable

      explanation (`details`), and a set of intelligence flags (disposable, role account,

      free service, spam-trap, gibberish, offensive). When the input domain is misspelled

      a corrected suggestion is returned in `emailSuggested`.


      The GET form is convenient for ad-hoc validation, link-time integrations, and

      spreadsheets / no-code tools. U'
  - info:
      name: Verify Email Address (POST)
      type: http
    http:
      method: POST
      url: https://emailverifierapi.com/v2/
      params:
      - name: apiKey
        value: ''
        type: query
        description: Customer API key.
      - name: xml
        value: ''
        type: query
        description: Set to `true` to receive an XML response payload instead of JSON.
      body:
        type: form-urlencoded
        data:
        - name: email
          value: ''
    docs: 'Same as the GET form but accepts the email address either as a query parameter or

      as a form-encoded body. Recommended for production server-to-server usage so that

      addresses do not leak into proxy access logs.'
bundled: true