Bounces quietly wreck your sender reputation, and a name with no address stalls the whole campaign. The Email API checks deliverability at the mailbox level, finds the work email you are missing, and resolves the person behind any address. One key, one JSON envelope.
{ "email": "[email protected]", "deliverable": true, "reason": "mailbox_accepts", "catch_all": false }
{ "email": "[email protected]", "found": true, "confidence": "high", "catch_all": false }
You know the person and the company, but not the address. Give a name and a domain, or a profile URL, and get back a deliverable work email with a confidence score. No pattern guessing, no test sends against a real inbox.
{ "status": "processing", "total": 1000, "resolved": 847, "next_cursor": 847 }
Checking a list one call at a time does not scale. Submit up to a thousand addresses or people in a single job and stream the verdicts back as they land, so nothing blocks on any one row.
{ "found": true, "confidence": "high", "person": { "full_name": "Ada Meyer", "title": "VP Engineering", "location": "Berlin, DE" }, "current_company": { "name": "Vercel", "industry": "Software", "size": "201-500" } }
A work email lands in your funnel with nothing attached to it. Reverse resolves the person and their company from that one string, so a bare signup arrives already enriched. Consumer, role, and throwaway addresses are turned away before any charge.
{ "domain": "acme.com", "count": 2, "prospects": [ { "email": "[email protected]", "first_name": "Jane", "last_name": "Doe" }, { "email": "[email protected]", "first_name": "Marc", "last_name": "Smith" } ] }
Start from a company instead of a person. Ask for a domain and get the contacts already on file, either every known address or verified only, so you can build an account list without a single name to begin with.
Renidly goes past the format and checks the mailbox itself. Every address comes back deliverable, undeliverable, or risky, with the reason attached: a disposable provider, a role inbox, a forwarding relay, a domain with no mail servers, or a catch-all it cannot confirm.
Some domains accept mail for every address, real or not. Renidly detects them and returns risky rather than a false deliverable, so you never send on a guess dressed up as a confirmation.
Check a single address inline at a signup form, or hand off a list of up to a thousand as one background job and collect the results as they stream in. The verdict shape is identical either way.
Validation errors, authentication failures, rate-limit rejections, and repeat lookups served from cache are never charged. Credits move only when a call does real work and returns a result.
One typed client, the same key across all three APIs. No SDK? It is one authenticated HTTPS call and one JSON envelope.
# verify one addressv = renidly.emails.verify("[email protected]")→ deliverable=True reason=mailbox_accepts # find a work email from a name and companyrenidly.emails.find(first_name="Ada", last_name="Meyer", domain="vercel.com")→ found=True confidence=high$ ▍A catch-all comes back as risky, not a false deliverable. You get the truth, including the cases where certainty is simply not possible.
The same X-renidly-apikey header and the same JSON envelope as the Data and Live APIs. Mix all three in a single integration.
Method names, parameters, and returns autocomplete in your editor, with retries, pagination, and batch jobs already handled.
GDPR and CCPA aligned handling on every lookup, with an audit trail behind it.
Every address in your sequences becomes one that is mailbox confirmed before it ships, the bounce rate that was throttling your domain falls off a cliff, and deliverability stops being a fire drill.
Get your API key on signup. Pay only for what you call.
100 credits on signup
Pay-as-you-go top-ups
Negotiated + SLA