Validate a single email

Checks whether an email address is deliverable. The response tells you the
result (valid, invalid, or risky), the confidence level, the mail
provider, and whether the domain is a catch-all.

Cost: 1 credit. You are not charged if the result is risky.

Check if a lead is behind a Secure Email Gateway (SEG)

A Secure Email Gateway is a filtering service, such as Proofpoint or Mimecast,
that sits in front of a company's mailboxes. You do not need a separate
endpoint to check for one. Every validation result already includes it:

Field	Type	Meaning
`hasSEG`	boolean	`true` when the email's domain routes mail through a gateway
`segProvider`	string	Which gateway it is. Only present when `hasSEG` is `true`

How to check a lead

Send the lead's email to this endpoint (or to the batch endpoint for a list).

Read data.hasSEG in the response.

If it is true, read data.segProvider to see which gateway protects the domain.

{
  "email": "sarah.chen@stripe.com",
  "result": "valid",
  "hasSEG": true,
  "segProvider": "proofpoint"
}

Possible segProvider values

Value	Gateway
`proofpoint`	Proofpoint
`mimecast`	Mimecast
`barracuda`	Barracuda
`cisco`	Cisco Secure Email (IronPort)
`forcepoint`	Forcepoint / MessageLabs
`sophos`	Sophos
`trendmicro`	Trend Micro
`symantec`	Symantec Email Security.cloud
`mcafee`	McAfee / MX Logic
`postini`	Google Postini
`microsoft_atp`	Microsoft 365 built-in filtering

Good to know

The check is done per domain, from the domain's MX records. Every email on
the same domain gets the same answer.

microsoft_atp is returned for every domain hosted on Microsoft 365. If you
only care about third-party gateways, treat microsoft_atp as no gateway.

The email is still validated when a gateway is found. hasSEG is extra
information and does not change result.

If the domain could not be looked up, result is risky with the message
DNS lookup failed - could not verify domain, and hasSEG is false. Treat
that case as "not checked" and try again later.

There is no extra cost. The normal validation price applies.

Request

Authorization

API Key

Add parameter in header

x-api-key

Example:

x-api-key: ********************

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Body Params application/jsonRequired

Examples

{ "success": true, "data": { "email": "sarah.chen@stripe.com", "result": "valid", "message": "The mailbox exists and is accepting mail", "isCatchAll": false, "isFederated": false, "hasSEG": true, "segProvider": "proofpoint", "provider": "GOOGLE", "confidence": "high" }, "meta": { "requestId": "664f2b3c9a1e4d0012abcdef", "creditsUsed": 1, "creditsRemaining": 24999, "processingTimeMs": 387 } }

Validate a single email

Check if a lead is behind a Secure Email Gateway (SEG)#

Request

Responses

Check if a lead is behind a Secure Email Gateway (SEG)