Mail Checker API

Fast, accurate email validation & deliverability checks.

API FAQ
Get API Key Buy Credits
What can you do?
Cut bounce rates

Validate before you hit “Send”.

Block disposable sign-ups

Stop throwaway in registrations & marketing lists.

Improve sender reputation

Better email hygiene = higher inbox placement.

Try Live
99.9 % Uptime
1898.8ms Response
20 req/s
0.005 Credits / request

Validate Email 


POST https://api.yeb.to/v1/mailchecker
ParameterTypeReq.Description
api_key string yes Your API key
email string yes Email to validate

Example

curl -X POST https://api.yeb.to/v1/mailchecker \
  -H "Content-Type: application/json" \
  -d '{
  "api_key": "YOUR_KEY",
  "email":   "[email protected]"
}'

Response Example

{
  "email": "[email protected]",
  "trusted": "high",
  "score": 7,
  "risk": "low",
  "knownProvider": true,
  "recommend": []
}
{"error":"Missing \"email\" parameter","code":422}

Response Codes

CodeDescription
200 SuccessRequest processed OK.
400 Bad RequestInput validation failed.
401 UnauthorizedMissing / wrong API key.
403 ForbiddenKey inactive or not allowed.
429 Rate LimitToo many requests.
500 Server ErrorUnexpected failure.

Frequently Asked Questions

It uses multi-step DNS, MX and heuristics to approximate deliverability without SMTP banners, keeping it fast and safe.

No. We hash emails in flight for analytics; the plain address is never written to disk.

Yes. Every request, even those resulting in errors, consumes credits. This is because your credits are strictly tied to the number of requests, regardless of success or failure. However, if the error is clearly due to a platform problem on our end, we’ll recover those credits for you.

Contact us at [email protected]. We take feedback seriously—if your bug report or feature request is meaningful, we can fix or improve the API quickly and grant you 50 free credits as a thank you.

It depends on the API and sometimes even on the endpoint. Some endpoints use data from external sources, which may have stricter limits. We also enforce limits to prevent abuse and keep our platform stable. Check the docs for the specific rate limit for each endpoint.

We operate on a credit system. Buy once—credits never expire. They’re non-refundable units for making API calls (requests). Simple, fair, and you top up only when you need more.

Every HTTP call is one request. Each request consumes a number of credits depending on the endpoint. In most cases, you can make thousands of requests with just one credit—but always check each endpoint for its cost.

Yes. Your credits never expire until you use them, but they are non-refundable.

Credits are non-refundable. Only buy what you need—you can always top-up later. If we screw up and it costs you, we’ll fix it.

Prices are set in credits, not dollars. Each endpoint lists its own cost—see the “Credits / request” badge above. You’ll always know exactly what you’re spending.
← Back to APIs