Emailable API
★ 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.
Use for: I need to verify an email address before sending, Submit a batch of 50,000 emails for verification, Check the status of a running batch verification job, Get the remaining credits on my Emailable account
Not supported: Does not handle email sending, mailbox provisioning, or contact storage — use for email-address verification and deliverability scoring only.
Jentic publishes the only available OpenAPI specification for Emailable API, keeping it validated and agent-ready. Emailable provides email-verification and deliverability scoring, and the API exposes 4 focused endpoints: single email verification, batch verification submission, batch status lookup, and account information. Authentication is an API key passed in the X-API-Key request header against https://api.emailable.com. The narrow surface makes Emailable easy to wire as a step in a marketing pipeline or a form-submission handler.
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.
1
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 | sh2
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 instanceJentic 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}
Read the connected account's plan, credits, and usage via GET /v1/account
Use Emailable as a real-time gate on signup forms to reject undeliverable addresses
Run a list-cleaning job before a major email campaign to reduce bounce rates
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
The Emailable 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 'bulk verify a list') and Jentic returns the matching Emailable operation with its input schema, so the agent picks the right endpoint without browsing the docs.
Time to first call
Direct integration: 1-2 hours to wire X-API-Key auth and a polling loop on /v1/batch. Through Jentic: under 10 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 at https://app.jentic.com/sign-up.
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.
GET STARTED