Menu

Documentation

Email Verifier API

Check email addresses before you write to them. That way bounces drop and your lists stay clean.

Email verification
https://api.flowdata.one/v1/email-verification/{email}

OpenAPI file for this area

Quick start

FlowData key
This API belongs to FlowData and uses its own keys (fd_...), which you create in the dashboard under API keys. FlowSuite keys (pk_..., at_...) keep working, but we recommend a FlowData key.
Key in the header only
Send the key only in the header Authorization: Bearer fd_..., never in the URL.
External verification services
If our own checks are not conclusive, the address is sent to connected verification services (Emailable, Hunter, Leadrocks).
Security notice
Never use API keys in frontend code. In production, route requests through your own backend.

Overview

The Email Verifier API checks an email address in several stages and stops as soon as a stage gives a clear result:

  1. Syntax according to RFC 5321/5322, including internationalised domains
  2. Stored result for the same address, if still valid
  3. Mail server of the domain (MX records, null MX according to RFC 7505, A/AAAA fallback)
  4. Disposable domains and known catch-all domains
  5. Mailbox check through connected verification services

It also flags role addresses such as info@ or accounting@.

API endpoints

GET
/v1/email-verification/{email}

Verify an email address

Verifies an email address. result is safe (deliverable), risky (deliverable but uncertain), invalid (not deliverable) or unknown (cannot be determined, not billed). reason states why: accepted, catch_all, role_account, disposable, invalid_syntax, invalid_domain, null_mx, rejected, low_quality, unverifiable, processing_objected (the person concerned has objected to the processing of their data) or dns_unavailable. checks contains the individual checks (syntax, mail server, mail provider, disposable domain, role address, catch-all). The existing fields remain: status is valid if mail can be sent to the address, otherwise risky, invalid, disposable or unknown. source shows where the result comes from: DB (stored result), NA (own check) or a verification service (LR, HU, EA). The API answers a syntactically invalid address with HTTP 400.

Bearer fd_… 9.00 EUR per 1,000 successful requests

Path parameters

Name Type Description
email string
Required
Email address to verify
curl -X GET "https://api.flowdata.one/v1/email-verification/max@example.com" \
  -H "Authorization: Bearer fd_YOUR_KEY" \
  -H "Accept: application/json"
use Illuminate\Support\Facades\Http;

$response = Http::withToken('fd_YOUR_KEY')
    ->get('https://api.flowdata.one/v1/email-verification/max@example.com');

$data = $response->json();
const response = await fetch('https://api.flowdata.one/v1/email-verification/max@example.com', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer fd_YOUR_KEY',
    'Accept': 'application/json',
  },
});

const data = await response.json();
import requests

headers = {
    'Authorization': 'Bearer fd_YOUR_KEY',
    'Accept': 'application/json',
}

response = requests.get(
    'https://api.flowdata.one/v1/email-verification/max@example.com',
    headers=headers,
)

data = response.json()
{
    "email_address": "user@example.com",
    "status": "valid",
    "source": "NA",
    "result": "risky",
    "reason": "catch_all",
    "checks": {
        "syntax": true,
        "mx": "ok",
        "mail_provider": "other",
        "disposable": false,
        "role_account": false,
        "catch_all": true
    }
}

Validation features

Syntax

  • Check according to RFC 5321/5322
  • Internationalised domains (IDN)
  • Length limits for address, local part and domain

Domain

  • MX records and mail provider of the domain
  • Null MX (domain does not accept mail)
  • Domains without a mail server
  • Catch-all domains, once a verification service has detected them

Mailbox

  • Check through connected verification services, only if our own checks are not conclusive
  • Stored results are reused for 3 to 90 days depending on the result

Quality

  • Disposable domains (list updated weekly)
  • Role addresses such as info@, support@ or accounting@

One key is all it takes to start.

Create a key and call the API. Client info is free; everything else is billed per successful request.

Create an API key Documentation

FlowData is aimed exclusively at businesses and self-employed professionals.