Email

Check if an email uses a free provider · Email API

GET/email/check
Free

Classify one email address as `business`, `free`, or `invalid`. The domain is matched exactly against 4,768 free email provider domains (the list HubSpot forms block with "Block free email providers", snapshot 2026-10-10); the response also flags role mailboxes (info@, sales@, noreply@) and explains syntax failures. Runs without DNS or SMTP probes, so it is instant and costs 0 credits. Use it to gate signup and lead forms on work emails.

Request
curl https://api.unifapi.com/email/check?email= \
  -H "Authorization: Bearer $UNIFAPI_KEY"

Parameters

emailqueryrequired
Email address to classify, e.g. `jane@gmail.com`.
The parameter for this Email operation. Use the URL-visible slug or id described in the docs.
Overview

This operation is part of the Email API in the email category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs Email public data but should still keep one API key, one account balance, and one predictable JSON contract across social, live public-data sources.

Common agent workflows

  • Look up public Email data for agents that need reliable open-web context.
  • Give an AI agent a stable Email data source without building a per-platform integration.
  • Normalize Email responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
  • This operation has a zero-credit multiplier, so successful responses include zero-charge billing metadata.
  • A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.

Response status codes

200400401402404429500502503

Billing

This operation is free: it has a zero-credit multiplier and still returns billing metadata with zero credits charged.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Response fields

Fields in the data object

A successful Check if an email uses a free provider call returns one data object with these fields.

inputstring
The address as received, trimmed.
emailstring | null
Lowercased address; null when the syntax is invalid.
local_partstring | null
Lowercased part before the `@`.
domainstring | null
Lowercased domain; internationalized domains are converted to punycode.
is_valid_syntaxboolean
is_free_providerboolean | null
The domain is on the free email provider list. Null when the syntax is invalid.
is_role_accountboolean | null
The local part (ignoring any `+tag`) is a shared mailbox such as `info`, `sales`, `support`, or `noreply`. Null when the syntax is invalid.
verdictstring
`free` — the domain is on the free email provider list. `business` — valid syntax and the domain is not on the list (a classification, not a deliverability check). `invalid` — the address or domain fails the syntax check.
invalid_reasonstring | null
Run it

Agents & Skills built on Email

You rarely call Check if an email uses a free provider by hand. These prebuilt agents and skills already read Email data inside Claude or Codex — start from one of them, or call this endpoint yourself.