FlowData

How do I check an email address with the Email Verifier?

Published on 10. November 2026

The Email Verifier tells you whether you can send to an email address. It's useful for newsletter sign-ups, contact forms, or before you use an older address list. It helps you avoid bounces and protects the reputation of your sending domain.

The request

A check is a GET to /v1/email-verification/ with the address at the end of the path. Your key goes only in the Authorization header, never in the URL.

curl "https://api.flowdata.one/v1/email-verification/jane.doe%40example.com" \
  -H "Authorization: Bearer fd_YOUR_KEY"

URL-encode the address, especially if it contains special characters. A + in the local part, as in anna+newsletter@example.com, becomes %2B, and the @ may be written as %40. Most programming languages have a built-in function for this, such as rawurlencode() in PHP. Domains with non-ASCII characters, such as info@müller.example, are recognized.

The response

{
  "email_address": "jane.doe@example.com",
  "status": "valid",
  "source": "LR",
  "result": "safe",
  "reason": "accepted",
  "checks": {
    "syntax": true,
    "mx": "ok",
    "mail_provider": "other",
    "disposable": false,
    "role_account": false,
    "catch_all": false
  }
}
  • email_address: the address that was checked.
  • status: the simple answer to whether you can send: valid, risky, invalid, disposable or unknown.
  • result: the finer assessment: safe, risky, invalid or unknown.
  • reason: why the result came out that way, for example accepted, catch_all or rejected.
  • checks: the individual checks: syntax, mail server, mail provider, disposable domain, role address and catch-all. For older stored results, reason and checks can be null.
  • source: where the result came from. DB is a stored result, NA is FlowData's own check, and any other code names the connected verification service.

What the values mean and how to handle them is covered in What do the Email Verifier results mean and how should I handle them?.

How long does a check take?

FlowData checks what it can itself first: syntax, stored result, the domain's mail server, disposable domains and known catch-all domains. That's quick. Only if this isn't enough does it ask connected verification services one after another until one gives a clear answer. That can take several seconds, and over a minute in the worst case. So set a generous timeout on your request, and for sign-ups, check addresses in the background rather than while the person waits on the page.

If the address has an invalid format

Addresses with an invalid format, for example without an @, are rejected straight away with HTTP 400:

{"error":"Invalid email address"}

A domain without a mail server, on the other hand, is not a format error. Those addresses get HTTP 200 with "result": "invalid".

What does a check cost?

Billing is based on usage, with the price set per 1,000 successful checks. A stored result counts as a check too. You are not charged for requests with the result unknown, for addresses rejected with HTTP 400, or for requests that fail for any other reason. Amounts are on the pricing page, and the prices that apply to your team are in FlowData under Billing.

If your balance is too low or a spend limit has been reached, the API answers with HTTP 402 and the code insufficient_quota or spend_limit_exceeded. Without a valid key you get HTTP 401. There's more in FlowData API error messages and rate limits.

Good to know

Was this article helpful?

Back to Email Verifier