Menu

Email verification

Check before you send

FlowData checks syntax, mail servers, disposable domains and role addresses itself. If that does not settle it, the chain asks external verification services until one gives a clear answer.

For businesses and self-employed professionals only

  • Check 9.00 EUR per 1,000 successful requests
GET /v1/email-verification/max@example.com
curl
curl "https://api.flowdata.one/v1/email-verification/max@example.com" \
  -H "Authorization: Bearer fd_YOUR_KEY"
Response
200
{
    "email_address": "max@example.com",
    "status": "invalid",
    "source": "NA",
    "result": "invalid",
    "reason": "null_mx",
    "checks": {
        "syntax": true,
        "mx": "null_mx",
        "mail_provider": "other",
        "disposable": false,
        "role_account": false,
        "catch_all": null
    }
}

A real API response.

Endpoints

The key goes in the header, not the path. The response gives the result, the reason in reason and the individual checks.

GET /v1/email-verification/{email} Checks one address and answers with the result right away.

The verification chain

The result

The result field has one of four values, reason gives the cause.

The email verification view in the FlowData dashboard
Every check appears with its result in your team's log.

Screenshots show the FlowData interface in German, with the example data of a fictional company.

What to expect

The address only leaves FlowData when our own checks cannot decide, then it goes to Leadrocks, Hunter or Emailable. We store the result, and the checked address appears in the usage counter.

Frequently asked questions

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.