Customer API

Email Finder Verifier API docs

One endpoint to find a verified work email from a name + domain, one to verify a known address. Stable response shape. Ready for Clay, n8n, enrichment scripts, and internal tools.

Get API key Download OpenAPI JSON

Quickstart

Base URL: https://my.emailfinderverifier.com

Auth

X-API-Key header

Trial

10,000 verified found emails

Billing event

Only verified found results

curl

curl -G "https://my.emailfinderverifier.com/api/v1/find" \
  --data-urlencode "domain=manasai.co" \
  --data-urlencode "first_name=Reid" \
  --data-urlencode "last_name=Hoffman" \
  -H "X-API-Key: YOUR_API_KEY"

Authentication

Every API call requires your key in the X-API-Key header.

Create API keys from the dashboard.
Do not expose keys in browser-side code.
Revoked, paused, expired, or disabled accounts cannot call the API.

Find email

GET /api/v1/find

Finds a verified work email from first name, last name, and company domain.

Query parameters

Name	Required	Description
domain	Yes	Company domain, for example manasai.co.
first_name	Yes	Person's first name.
last_name	Yes	Person's last name.

Request

curl -G "https://my.emailfinderverifier.com/api/v1/find" \
  --data-urlencode "domain=manasai.co" \
  --data-urlencode "first_name=Reid" \
  --data-urlencode "last_name=Hoffman" \
  -H "X-API-Key: YOUR_API_KEY"

Response

{
  "email": "reid@manasai.co",
  "found": true,
  "domain": "manasai.co",
  "reason": "OK",
  "pattern": "firstname",
  "attempts": 2,
  "confidence": "high",
  "is_catchall": false
}

A trial credit is used only when found=true, confidence=high, is_catchall=false, and email is populated.

Verify email

GET /api/v1/verify

Checks whether a single email appears valid. Use this when you already have a candidate email.

Query parameters

Name	Required	Description
email	Yes	Email address to verify.

Request

curl -G "https://my.emailfinderverifier.com/api/v1/verify" \
  --data-urlencode "email=reid@manasai.co" \
  -H "X-API-Key: YOUR_API_KEY"

Response

{
  "email": "reid@manasai.co",
  "status": "valid",
  "reason": "Verified via SMTP",
  "mx_host": "worker",
  "smtp_code": 250
}

Credits and limits

Month 1 includes 10,000 verified found emails.
No trial credit is used for not found, invalid, unknown, catch-all, blocked, or rate-limited results.
Verification calls do not use found-email credits.
There is no daily found-email cap in month 1, but short-window safety limits still protect the service.
After 10,000 verified found emails or 30 days, the account pauses until it is activated again.

Errors

Status	Meaning	Fix
400	Missing or invalid input.	Check required query parameters.
401	Missing or invalid API key.	Create a key in the dashboard and send it in X-API-Key.
403	Account paused, expired, disabled, or out of credits.	Check dashboard status or contact Up.
429	Short-window safety limit reached.	Retry after a short delay.
500	Unexpected server error.	Retry. If it repeats, share the request with Up.

Error shape

{
  "detail": {
    "error": "Invalid or missing API key",
    "code": "INVALID_API_KEY"
  }
}

OpenAPI

The customer-safe OpenAPI file is available here:

Spec URL

https://emailfinderverifier.com/docs/openapi.json

Import this into Swagger, Postman, Insomnia, Stoplight, or any OpenAPI-compatible docs tool.