Skip to main content

Introduction

YesWeCheck verifies an email address and returns a verdict you can act on: can you write to it, and at what risk? Each verification runs a series of checks (syntax, DNS, disposable address, typo, trap domain, role account, noreply address, SMTP dialogue…) and returns the details of each one.

Four ways to integrate​

What you can access with an API key​

The public API, the one a server calls with a ywc_live_… key, covers verification and input assistance:

EndpointPurposeAuthentication
POST /v2/email/validateVerify an addressAPI key
POST /v2/email/enrichInfer first name, last name, gender, presumed ageAPI key
POST /v2/email/suggest/localpartSuggest local parts from a nameAPI key
POST /v2/email/suggest-firstname · suggest-lastnameAutocomplete a first name or last nameAPI key
GET /v2/email/suggest/domain/countriesCountries covered by domain suggestionsAPI key
POST /v2/email/suggest/domainAutocomplete a domain (gmail.com, orange.fr…)API key or widget
POST /v2/email/suggest/typo-domainDetect a typo in the domainAPI key or widget
POST /mcpAI assistants' MCP server: verification, batches, B2B search, creditsAPI key or OAuth
GET /v2/billing/catalogPlans and credit packs, prices excl. VATNone
GET /healthAPI statusNone

Each endpoint is described in detail in the API reference.

What you manage from the dashboard

Creating API keys, bulk processing, widgets, allow and block lists, validation policies and billing are all managed from app.yeswecheck.fr. Their HTTP routes only accept a dashboard session: an API key gets 401. So they are not part of the public API documented here. One exception: AI assistants start and track batches, and read the balance, through the MCP server's tools.

The essentials in five points​

  1. One base URL: https://api.yeswecheck.fr/v2. Only /health, /status and the MCP server (/mcp) are served outside the /v2 prefix.
  2. One header: Authorization: Bearer ywc_live_…. The X-API-Key header is not read. See Authentication.
  3. SMTP is set on the key, not in the request: a key created with SMTP enabled runs it on every call; a key without SMTP never runs it. See Checks.
  4. A credit is only charged if SMTP was enabled and the final verdict is not unknown. All other checks are free. See Credits.
  5. The verdict is in result (valid, risky, invalid, unknown), along with a score from 0 to 100. See Verdicts and score.
Dashboardapp.yeswecheck.fr
Platform statusstatus.yeswecheck.fr
OpenAPI specificationdocs.yeswecheck.fr/openapi.yaml
Support[email protected]