EmailListVerify API

Name: EmailListVerify API API
Brand: EmailListVerify API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey4 EndpointsREST

For Agents

Validate single email addresses, submit bulk lists, check disposable status, and poll bulk-job progress with EmailListVerify. Authenticated with an API key in the X-API-Key header.

Connect the EmailListVerify API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EmailListVerify API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with EmailListVerify API API.

Verify a single email synchronously via GET /api/verifyEmail

Submit a bulk list of emails for verification with POST /api/verifyApiEmailList

Poll bulk-verification job status at GET /api/getApiFileInfo

Check whether a single address comes from a known disposable domain via GET /api/disposable

GET STARTED

Start building with EmailListVerify API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for EmailListVerify API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for EmailListVerify API, keeping it validated and agent-ready. EmailListVerify is an email-validation service exposing 4 endpoints: single-email verification, bulk-list submission, bulk-file status lookup, and a disposable-email check. Authentication is an API key in the X-API-Key request header against https://apps.emaillistverify.com. The narrow surface is purpose-built for cleaning email lists before campaigns and rejecting disposable signups in real time.

Use Cases

Patterns agents use EmailListVerify API API for, with concrete tasks.

★ Real-Time Disposable Email Rejection

Block disposable and throw-away email signups by calling GET /api/disposable on the submitted address before account creation. The disposable check returns a boolean quickly and is cheaper than a full verification, so it suits high-traffic signup forms. Suitable for any signup flow seeing thousands of submissions per day where account quality matters.

On signup, call GET /api/disposable with email=user@example.com; if disposable=true, reject the form and prompt the user for a permanent email

Pre-Campaign List Cleaning

Clean a recipient list before a marketing campaign by uploading the addresses with POST /api/verifyApiEmailList, polling GET /api/getApiFileInfo until complete, and filtering down to verified addresses. This is the recommended flow for lists larger than a few hundred where the synchronous verifier would be too slow or expensive.

POST a 25,000-address list to /api/verifyApiEmailList, poll /api/getApiFileInfo every minute until status=complete, then download the verified subset

Inline Verification on CRM Import

When importing leads into a CRM, run each address through GET /api/verifyEmail before creating the contact record so the CRM only holds deliverable addresses. The synchronous endpoint returns a status that classifies the address (deliverable, undeliverable, risky, unknown) and lets the import job make a deterministic accept-or-skip decision.

For each lead in the import queue, call GET /api/verifyEmail and only create the contact if status is 'deliverable'

AI Agent Integration via Jentic

Build an AI lead-enrichment agent that takes raw leads from a webform, validates each email through EmailListVerify, and forwards only deliverable leads to the sales pipeline. Through Jentic, the agent searches by intent, loads the verify schema, and executes without holding the X-API-Key in its prompt.

Search Jentic for 'verify a single email address with EmailListVerify', load the schema for GET /api/verifyEmail, and verify the latest webform email before creating a CRM lead

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for emaillistverify api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/verifyEmail

Verify a single email address

POST

/api/verifyApiEmailList

Submit a bulk list for verification

GET

/api/getApiFileInfo

Get bulk-verification file status

GET

/api/disposable

Check if an email is disposable

GET

/api/verifyEmail

Verify a single email address

POST

/api/verifyApiEmailList

Submit a bulk list for verification

GET

/api/getApiFileInfo

Get bulk-verification file status

GET

/api/disposable

Check if an email is disposable

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The EmailListVerify X-API-Key is stored encrypted in the Jentic vault (MAXsystem) and injected at execution time. Agents never hold the raw key in prompts or memory.

Intent-based discovery

Agents search by intent (e.g. 'verify a single email' or 'check if email is disposable') and Jentic returns the matching EmailListVerify operation with its input schema.

Time to first call

Direct integration: 1-2 hours to wire X-API-Key auth and a poll loop for /api/getApiFileInfo. Through Jentic: under 10 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Emailable API

Emailable is a competing email-verification service with similar single and batch endpoints

Pick Emailable when its SLA or pricing better fits the project; pick EmailListVerify when the disposable-only endpoint is wanted as a cheap pre-filter.

Alternative

ZeroBounce API

ZeroBounce offers verification with deeper data points like activity and IP geolocation

Choose ZeroBounce when you want enriched verification metadata; choose EmailListVerify for a smaller, faster surface.

Alternative

NeverBounce API

NeverBounce focuses on accept-rate guarantees for cleaned lists

Use NeverBounce when an accept-rate guarantee is a procurement requirement; use EmailListVerify as a simpler 4-endpoint replacement.

FAQs

Specific to using EmailListVerify API API through Jentic.

Why is there no official OpenAPI spec for EmailListVerify API?

EmailListVerify publishes its API reference as HTML at emaillistverify.com/api rather than as a versioned OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call EmailListVerify via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the EmailListVerify API use?

EmailListVerify uses an API key in the X-API-Key request header. Through Jentic, the key is stored encrypted in the vault and injected at execution time so the agent never sees the raw key in its prompt or logs.

Can I check whether an email is disposable?

Yes. GET /api/disposable returns a boolean indicating whether the address comes from a known disposable-email provider, which is the fastest way to block throw-away signups without spending a full verification credit.

How do I bulk-verify a large list?

POST /api/verifyApiEmailList with the list returns a job identifier, and GET /api/getApiFileInfo reports the job status. Poll at one-minute intervals for lists larger than 10,000 addresses.

How do I verify an email through EmailListVerify via Jentic?

Run the Jentic search query 'verify a single email address with EmailListVerify', load the input schema for GET /api/verifyEmail, then execute with the email to check. Jentic injects the X-API-Key at execution time.

What is the difference between the single verify and disposable endpoints?

GET /api/verifyEmail performs a full deliverability check (syntax, domain, mailbox) and returns a status like deliverable or undeliverable; GET /api/disposable only flags whether the domain is on the disposable list. Use the disposable endpoint as a cheap pre-filter and the verify endpoint when full deliverability matters.