canonical: https://jentic.com/apis/emailable.com/emailable

# Emailable API

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.

## For AI 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.

## Scope

Does not handle email sending, mailbox provisioning, or contact storage - use for email-address verification and deliverability scoring only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example 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

| 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 |

## Key resources

- **Verification** — Single email verification with deliverability state and score
- **Batch** — Submit and check status of bulk verification jobs
- **Account** — Read account plan, credits, and usage

## Why Jentic

- **Setup:** Wiring Emailable by hand means handling its API-key auth, setting the X-API-Key header on every call, and polling batch jobs yourself. Through Jentic you install once, import the Emailable API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Emailable verification takes its target as a request or query value rather than a resource id in the URL path, so scope the agent by operation: limit it to the calls it needs, such as GET /v1/verify and POST /v1/batch. You choose the operations it may call, so anything outside that set is not included unless you add it.
- **Credential handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **ZeroBounce API** — ZeroBounce is a competing email-verification service with similar single and batch endpoints
- **NeverBounce API** — NeverBounce offers similar verification scoring and bulk processing
- **SendGrid Email Validation API** — SendGrid validates emails inside its sending pipeline; Emailable validates before the list reaches the sender

## FAQ

### 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.