HomeUse casesVerify website signups
Check an email before you save it
From your signup form's backend, send the submitted email to the verify API. If it comes back verified, carry on. If not, ask the person to retype it. Then run your old signups through a CSV upload to see what's already in your database.
Free while in beta. No card needed.
Key takeaways
- The job: check the email on a signup or trial form instead of trusting it.
- The result: signup lists you've checked, plus an audit of the old ones.
- The rule: never let a slow or failed check stop a real signup.
Last updated 16 Nov 2026
01The job
The job, and why it matters
A signup form takes whatever the person types. Typos get saved. Addresses that don't work get saved. The first email you send, the welcome message, bounces. Do that often enough and mailbox providers start to distrust your sending domain.
Checking at the form moves the fix to the moment the person is still on the page and can retype.
02The workflow
How to do it with EFV
Make a key for the form
In the dashboard, open API keys and create one named "Signup form". Keep it on your server. Never put it in a web page or app.
Call verify from your backend
When the form is submitted, send a GET request to the verify endpoint with the email and your key in the
X-API-Keyheader.Save the signup first, then check
Save the signup right away. Run the check in the background and flag the record with the result. If you must check inline, use a short timeout, like 10 seconds, and let the person through if it runs out.
Decide per answer
Verified: carry on. Not confirmed: ask the person to check the spelling, and let them continue if they say it's right. Timeout or error: keep the signup and check it later.
Store the result
Save
verifiedand the mail provider next to the user record, so lifecycle and sales emails can use it.Audit what's already there
Export your signups as a CSV. In Verify or find a list, choose Verify, pick the email column and start. Up to 5,000 rows a run.
Here's the call, in Node.js. It never throws, so a failed check can't stop a signup:
const KEY = process.env.EFV_API_KEY;
// Returns true, false, or null when the check couldn't run.
async function checkEmail(email, timeoutMs = 10000) {
try {
const url = "https://api.emailfinderverifier.com/api/v1/verify?email=" + encodeURIComponent(email);
const res = await fetch(url, { headers: { "X-API-Key": KEY }, signal: AbortSignal.timeout(timeoutMs) });
if (!res.ok) return null;
return (await res.json()).verified;
} catch (err) {
return null; // timeout or network error: keep the signup, check it later
}
}
For a background check, call it with a longer timeout, like checkEmail(email, 60000), and write the answer onto the user record. A null means "check again later".
New accounts can send one request a second and have five at once. If you expect more signups than that, ask in Slack first.
03Results
What the results mean
| Answer | What to do at the form |
|---|---|
verified: true |
Save and continue. |
verified: false |
Ask them to check the address. A real address can come back false, so don't hard-block. |
null (timeout or error) |
Keep the signup and check it later. |
Get a key and try the call. Free while in beta.
Sign up for free04FAQ
Questions, answered
01Should I block signups that come back false?
No. Ask the person to check the spelling, then let them continue. A real address can sometimes come back false. For a fuller setup, see how to block fake and temporary email signups.
02How long does the call take?
Some checks take several seconds. That's why we suggest saving the signup first and checking in the background. For an inline check, use a short timeout and let the person through if it runs out.
03Can I call it from the browser?
Don't. The key would be visible to anyone. Call it from your server.
04Does it work with catch-all domains?
Yes. Catch-all emails can come back verified: true. The result also tells you if the domain is catch-all.
05Should I check every signup?
Start with new signups, then audit the old ones with a CSV. If you get more than one signup a second, ask us in Slack first.
06What about signups I already saved?
Export them as a CSV and verify them in the web app. It's a good first step, since it shows the size of the problem.
06Keep going
Where to next
06Start today
Get a key and test the signup check
Sign up with email or Google. No card. Your key and a ready-made first request are waiting. Need more later? Message us on Slack.