Reference & Lookup Data · Integration
Emailable
Add Emailable to your product for your customers, and give your AI agents governed access to it.
Emailable's single verification endpoint at api.emailable.com/v1/verify takes the address and the API key as query parameters and can return HTTP 249 rather than 200, meaning the check is still running against a slow mail server and you should retry the same address shortly, which is the single detail most integrations get wrong. Results carry a state of deliverable, undeliverable, risky or unknown, plus separate booleans for role addresses, free providers, disposable domains and accept-all servers, and treating risky as a hard bounce throws away deliverable contacts on accept-all domains. Bulk work goes through the batch endpoint, which returns an id immediately and is then polled, or reported to a callback URL, rather than blocking. Verification consumes credits per address and duplicates within a batch are still charged, so deduplicating before submission is worth doing. Nothing here is a subscriber list: the objects are lookups and results, so this belongs with reference data rather than with email sending. fastn holds each customer's Emailable key so verification draws on their credit balance, and keeps the connection maintained.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Emailable account so verification credits come from their balance.
Verify an address inline at signup and block undeliverable ones before the record is created.
Run a stored list through the batch endpoint and write the state back onto each contact.
Show accept-all and role-address flags so a customer can decide their own sending policy.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent verify a batch of addresses before a send and report the breakdown by state, with credit use audited per tenant.
Have an agent identify which contacts in a segment are risky or disposable and propose suppression.
Allow an agent to re-check addresses that previously returned unknown once the retry window has passed.
Example prompt
Run our new sign-ups from this week through Emailable and tell me how many are undeliverable.
Set up Emailable in 4 steps
- 01Enable the Emailable connector from your fastn dashboard.
- 02Have each customer authorise their own Emailable account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Emailable integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Emailable integration without building it. Your customers connect their own Emailable account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Emailable update is not your on-call problem.
- One integration serves your product and your agents. The same governed Emailable connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to Emailable, across other categories.
Salesforce
HubSpot
Notion
SnowflakeEmailable integration FAQ
How do I add an Emailable integration to my product?
Enable the Emailable connector in your fastn dashboard, then let each customer authenticate their own Emailable account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Emailable client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Emailable account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Emailable account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Emailable integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent verify a batch of addresses before a send and report the breakdown by state, with credit use audited per tenant.
Who maintains the Emailable integration?
fastn does. When Emailable changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does an Emailable lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Emailable results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Emailable is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Emailable integration?
A common starting point: let a customer connect their own Emailable account so verification credits come from their balance. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Emailable integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Emailable does not change your per-connector cost. You can start free with 3 connected accounts.
Add Emailable to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.