---
title: Email Risk Check API
slug: email-risk-check
url: https://apyhub.com/frolic/service/email-risk-check
provider: Hakimi Labs
categories: [Verification Kit, Safety Kit]
tags: [email-validation, email-verification, mx-records, disposable-email, signup-validation]
auth: api_key
version: 1.0
service_type: sync
endpoints: 1
atoms: 10
mcp: true
---

# Email Risk Check API

Validate an email address for syntax, MX records, disposable domains, and role accounts. Useful for reducing bounces and filtering risky signups.

## Endpoints

| Method | URL | Description | Atoms |
| --- | --- | --- | --- |
| GET | `https://api.eu.apyhub.com/frolic/email-risk-check/email/verify` | What it does Verifies an email address and returns a JSON object with validation details about the… | 10 |

## Endpoint reference

### Verify Email

`GET https://api.eu.apyhub.com/frolic/email-risk-check/email/verify` · 10 atoms · accepts `application/json` · returns `application/json`

| Parameter | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `email` | query | string | yes |  |

#### Quickstart

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

```bash
curl -X GET "https://api.eu.apyhub.com/frolic/email-risk-check/email/verify?email=alice@example.com" \
  -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.

```json
{
  "disposable": false,
  "domain": "example.com",
  "email": "alice@example.com",
  "free_provider": false,
  "has_mx": true,
  "mailbox_checked": true,
  "mx_records": ["mx1.example.com"],
  "reason": "valid",
  "result": "valid",
  "role_account": false,
  "valid_syntax": true
}
```

## About

## 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.

## Usage

Base URL: `https://api.eu.apyhub.com` (default region — see
`GET https://apyhub.com/api/public/regions` for the rest).

Authenticate with an ApyHub API key in the `apy-token` header.
Full docs and a live playground: https://apyhub.com/frolic/service/email-risk-check