apyhub
Back
▣ VERIFICATION KIT · SAFETY KIT

Email Risk Check API

What it does

Email Verification checks whether an email address is syntactically valid and whether its domain is set up to receive mail. Send an email in the query string and get back a structured result you can use to filter bad signups, reduce bounce rates, and flag risky addresses before you store or send to them.

The response includes the original email, the domain, and a result plus reason string for your application logic. You also get boolean checks for valid_syntax, has_mx, disposable, free_provider, role_account, and mailbox_checked, along with any mx_records discovered.

Use Email Verification when you need to validate registration forms, clean marketing lists, or gate access to workflows that depend on a reachable inbox. It is useful when you want to distinguish disposable addresses, role-based accounts like support@, and domains that do not publish MX records.

Keep the response close to your own rules: treat the booleans as machine-readable signals and use reason and result as the human-facing explanation when you decide whether to accept or reject an address.

GET
Verify Email
https://api.eu.apyhub.com/frolic/email-risk-check/email/verify

QUICKSTART

GUIDE

Quickstart

Check whether an email address looks valid by passing it as a query parameter.

curl -X GET "https://api.eu.apyhub.com/frolic/email-risk-check/email/[email protected]" \
  -H "apy-token: $APY_TOKEN"

What you'll get back

Returns a JSON object with fields such as disposable, domain, email, free_provider, has_mx, mailbox_checked, mx_records, reason, result, role_account, and valid_syntax, reflecting the email verification details.

{
  "disposable": false,
  "domain": "example.com",
  "email": "[email protected]",
  "free_provider": false,
  "has_mx": true,
  "mailbox_checked": true,
  "mx_records": ["mx1.example.com"],
  "reason": "valid",
  "result": "valid",
  "role_account": false,
  "valid_syntax": true
}
TRY ITLIVE · 10 ATOMS
Loading your default key…
The full key is used to call the gateway and stays in this tab — never sent to orbit or saved.

About this endpoint

What it does

Verifies an email address and returns a JSON object with validation details about the address and its domain, including syntax, MX status, and provider-related flags.

Query Parameter(s)

AttributeTypeMandatoryDescription
emailStringYesEmail address to verify. Maximum length: 320 characters.

Response

Returns a JSON object with disposable, domain, email, free_provider, has_mx, mailbox_checked, mx_records, reason, result, role_account, and valid_syntax fields. The response describes the verification outcome and related checks for the supplied email address.

AttributeTypeMandatoryDescription
disposableBooleanNoWhether the email domain is associated with a disposable email service.
domainStringNoDomain portion of the email address.
emailStringNoEmail address that was verified.
free_providerBooleanNoWhether the email belongs to a free email provider.
has_mxBooleanNoWhether the domain has MX records.
mailbox_checkedBooleanNoWhether mailbox-level checking was performed.
mx_recordsString ArrayNoMX records found for the domain.
reasonStringNoTextual reason associated with the verification result.
resultStringNoVerification result.
role_accountBooleanNoWhether the email is a role account.
valid_syntaxBooleanNoWhether the email address has valid syntax.
▣ COMMON ERRORS

Errors any endpoint can return

400bad_request

Required parameter missing or malformed body.

401unauthorized

API key missing, revoked, or not authorized for this service.

429rate_limited

Your plan's per-second rate exceeded. Retry with exponential backoff.

503upstream_busy

Backend temporarily unavailable. Try again in a few seconds.