Raw Reacher Backend

Advanced

Most users should use the Verify and Find endpoints. Those run the full engine (SMTP, the Microsoft login method, and proxy rotation) behind one key. The raw backend below is SMTP only, with no Microsoft method and no proxies. Use it only if you specifically need direct access.

The verification engine is also reachable directly at verify.bluauto.io. It takes a separate secret, sent in the x-reacher-secret header.

POST https://verify.bluauto.io/v1/check_email

Examples

cURL

curl https://verify.bluauto.io/v1/check_email \
  -X POST \
  -H "Content-Type: application/json" \
  -H "x-reacher-secret: YOUR_SECRET" \
  -d '{"to_email":"john@acme.com"}'

Python

import requests

resp = requests.post(
    "https://verify.bluauto.io/v1/check_email",
    headers={
        "Content-Type": "application/json",
        "x-reacher-secret": "YOUR_SECRET",
    },
    json={"to_email": "john@acme.com"},
    timeout=30,
)
print(resp.json()["is_reachable"])   # safe | risky | invalid | unknown

HTTP

POST /v1/check_email HTTP/1.1
Host: verify.bluauto.io
Content-Type: application/json
x-reacher-secret: YOUR_SECRET

{"to_email":"john@acme.com"}

How is_reachable is derived

The raw backend returns safe, not valid.

is_reachable	Condition
unknown	The SMTP check itself errored (dead MX, timeout, connection refused, or greylisted).
risky	SMTP succeeded and any of: disposable, role account, catch-all, or full inbox.
invalid	SMTP succeeded and any of: not deliverable, cannot connect, or disabled.
safe	SMTP succeeded and none of the above.

Your x-reacher-secret is in the app under Admin → API Key (owner only).