Emailable API

Name: Emailable API
Brand: Emailable API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey4 EndpointsREST

For Agents

Verify email addresses one at a time or in bulk and check deliverability scores via Emailable. Authenticated with an API key in the X-API-Key header.

Install Jentic One Beta

Connect the Emailable API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Emailable 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Emailable API.

Verify a single email address synchronously via GET /v1/verify

Submit a batch verification job for thousands of addresses with POST /v1/batch

Poll a batch's status and progress at GET /v1/batch/{batchId}

GET STARTED

Start building with Emailable API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Emailable API for, with concrete tasks.

★ Real-Time Signup Form Validation

Block undeliverable and disposable email addresses at signup by calling GET /v1/verify on the submitted email and rejecting the form when the result is undeliverable or risky. The single-verify endpoint returns synchronously in under a second for most addresses, which keeps the form-submit user experience snappy. Suitable for any signup form receiving thousands of submissions per day.

On form submit, call GET /v1/verify with email=user@example.com; if the response state is undeliverable, reject the form with a clear error

Pre-Campaign List Cleaning

Before a major email send, clean the recipient list with POST /v1/batch to reduce bounce rates and protect sender reputation. The batch endpoint accepts a CSV or list of addresses, returns a batch ID, and is paired with GET /v1/batch/{batchId} for status polling. Use the resulting deliverability scores to filter the send list down to verified addresses only.

POST a batch of 10,000 addresses to /v1/batch, poll /v1/batch/{batchId} every 30 seconds until status=complete, then download the verified subset

Account and Credit Monitoring

Operate Emailable as a budgeted line item by polling GET /v1/account on a schedule and alerting when remaining credits fall below a threshold. The account endpoint returns plan and credit data so a finance integration can charge back per team, and a paging integration can prevent verification stalls during a campaign.

Call GET /v1/account daily and post a Slack alert when credits remaining drop below 5,000

AI Agent Integration via Jentic

Build an AI lead-enrichment agent that takes a raw lead from a webform, verifies the email with Emailable, and only forwards leads with a deliverable score into the CRM. Through Jentic, the agent searches by intent, loads the verify schema, and executes without the X-API-Key entering the agent's prompt.

Search Jentic for 'verify a single email address', load the schema for GET /v1/verify, and verify the email from the latest webform submission

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/v1/verify

Verify a single email

POST

/v1/batch

Create a batch verification

GET

/v1/batch/{batchId}

Get batch verification status

GET

/v1/account

Get account information

GET

/v1/verify

Verify a single email

POST

/v1/batch

Create a batch verification

GET

/v1/batch/{batchId}

Get batch verification status

GET

/v1/account

Get account information

Why Jentic?

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

Credential isolation

Your Emailable API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'verify a single email' or 'bulk verify a list', and Jentic returns the matching Emailable operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Emailable API through Jentic.

Why is there no official OpenAPI spec for Emailable API?

Emailable publishes its API reference as HTML at emailable.com/docs/api rather than as a versioned OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call Emailable via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Emailable API use?

Emailable uses an API key passed 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 verify a single email synchronously?

Yes. GET /v1/verify accepts an email query parameter and returns a deliverability state and score in the same response, typically within a second. This is the recommended path for signup forms and inline checks.

How do I bulk-verify a list of emails?

POST /v1/batch with the list of addresses returns a batch ID, and GET /v1/batch/{batchId} reports progress and the final result. Polling at 30-second intervals is a sensible default for batches up to a few hundred thousand addresses.

How do I verify an email through Jentic?

Run the Jentic search query 'verify a single email address', load the input schema for GET /v1/verify, then execute with the email to check. Jentic injects the X-API-Key at execution time so the agent does not need to manage the credential.

How do I monitor my remaining credits?

GET /v1/account returns the plan and credit balance. Polling this endpoint daily and alerting when remaining credits fall below a threshold prevents verification stalls during high-volume campaigns.

Can I limit what my agent is allowed to do with the Emailable API?

Yes. Because you run Jentic One yourself, your own rules decide which Emailable operations and credentials the agent may use. Emailable takes its target email as a request or query value rather than a resource id in the URL path, so you scope the agent by operation: grant only the calls it needs, such as GET /v1/verify for single checks and POST /v1/batch with GET /v1/batch/{batchId} for bulk jobs, while withholding GET /v1/account. Any operation you do not add stays outside the agent's reach.