Integration notes for email verification

Use these notes alongside the provider’s maintained reference. This site teaches integration decisions; it does not sell separate API plans.

Authentication and request

Call GET /v1/verify on a trusted server. Send the key in X-API-Key and the address in the email query parameter. URL-encode the value, including + signs in aliases. Never put a live key in a browser bundle or a public URL.

curl --get 'https://api.easyemailverification.com/v1/verify' \
  -H "X-API-Key: $EEV_API_KEY" \
  --data-urlencode 'email=name+tag@example.com'

Interpret a processed request

HTTP 200 reports a processed request. Read result and reason before making a business decision. A valid result is not permission to email someone; unknown must not be treated as invalid.

SignalApplication action
result: invalidReview the rejection and typo suggestion.
result: unknownKeep for review; consider a later retry.
accept_all / disposableApply your risk policy; do not silently accept all contacts.
safe_to_sendOne verification signal, not a delivery guarantee.

Handle failures without losing their meaning

Plans and production

Production limits and billing belong to Easy. Confirm the current plan before launch; monitoring products are separate from the mailbox verification request. See current pricing.

Start with the sandbox · Full provider API reference