CleanContact
← Back to Knowledge

API Reference: The /validate Endpoint

The CleanContact API is a single authenticated endpoint. Send an address, get a verdict.

Request

Issue a GET request with the address as a query parameter and your API key in the X-API-Key header.

curl -H "X-API-Key: <your-key>" \
  "https://api.cleancontact.ru/validate?email=someone@example.com"

Response

A successful call returns 200 with the address you sent and a result object.

{
  "value": "someone@example.com",
  "result": {
    "status": "Good",
    "detail": "Mailbox accepts mail"
  },
  "suggest": ["someone@example.net"],
  "risk": {
    "gmailDotTrick": true,
    "aliasOf": "someone@gmail.com",
    "seenVariants": 2
  }
}

This example shows every field the endpoint can return. In an actual response, suggest and risk are each present only when relevant — see below.

The status field is one of:

  • Good — the mailbox exists and accepts mail.
  • Bad — the address does not exist or is rejected.
  • Unknown — no definitive answer was available in time.

Status codes

  • 200 — validation completed; read result.status for the verdict.
  • 400 — the email parameter was missing or malformed.
  • 401 — the API key is missing, unknown, or inactive.
  • 429 — too many requests; back off and retry.

Optional response fields

Two extra fields may appear next to result, depending on the address:

  • suggest — a likely correction when the domain looks like a typo of a trusted provider. See Typo Suggestions.
  • risk — a fraud signal when a Gmail mailbox has been submitted under several dotted spellings. See Gmail Dot Trick.