Quickstart: your first AuthFlame email check

This quickstart walks you from an API key to a working email check request, and shows how to act on the response inside your signup flow.

Prerequisites

An AuthFlame account
A live API key (prefixed with af_live_)
A tool that can send HTTP requests (curl, PowerShell, Node.js, Python, etc.)

1. Get your API key

Your API key grants full access to your AuthFlame account. Store it in an environment variable or secret manager, and rotate it immediately if exposed.

2. Send your first check

Post the email address you want to evaluate to the check endpoint.

curl -X POST https://api.authflame.com/v1/ \
  -H "Authorization: Bearer af_live_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"email": "test@example.com"}'

$headers = @{
  "Authorization" = "Bearer af_live_your_api_key"
  "Content-Type"  = "application/json"
}
$body = @{ email = "test@example.com" } | ConvertTo-Json

Invoke-RestMethod `
  -Uri "https://api.authflame.com/v1/" `
  -Method Post `
  -Headers $headers `
  -Body $body

const response = await fetch("https://api.authflame.com/v1/", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.AUTHFLAME_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ email: "test@example.com" }),
});

const result = await response.json();
console.log(result.summary.action);

import os
import requests

response = requests.post(
    "https://api.authflame.com/v1/",
    headers={
        "Authorization": f"Bearer {os.environ['AUTHFLAME_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={"email": "test@example.com"},
)

result = response.json()
print(result["summary"]["action"])

3. Read the response

A successful check returns a decision summary, a normalized address, and the signals that contributed to the score.

Response

{
  "summary": {
    "action": "ALLOW",
    "risk_score": 3,
    "risk_level": "low"
  },
  "normalized": {
    "raw": "test@example.com",
    "canonical": "test@example.com",
    "local_part": "test",
    "domain": "example.com",
    "subaddress": null,
    "has_dots_removed": false
  },
  "signals": {
    "syntax": { "valid_format": true },
    "entropy": { "score": 1.5, "suspicious": false },
    "domain": {
      "is_known_disposable": false,
      "is_known_free_provider": false,
      "has_mx": true,
      "is_catch_all": false,
      "is_role_account": false,
      "tld_risk_level": "low"
    }
  }
}

The three fields you almost always care about:

summary.action: ALLOW or BLOCK. Use it as the primary gate.
summary.risk_score: 0 to 100. Useful for custom thresholds or A/B tests.
normalized.canonical: The deduped form of the address. Store this to catch duplicate accounts.

Call AuthFlame before creating the user

Send the submitted email to /api/ from your backend, not the browser.

Branch on summary.action

ALLOW: create the account.
BLOCK: reject the signup with a generic error message.

Store the canonical email

Persist normalized.canonical alongside the raw address so you can detect duplicate signups later.

Need help? Reach the AuthFlame team through the AuthFlame website.

Get Started

Concepts

Quickstart: your first AuthFlame email check

Prerequisites

1. Get your API key

2. Send your first check

3. Read the response

​Prerequisites

​1. Get your API key

​2. Send your first check

​3. Read the response

​4. Wire it into signup

Prerequisites

1. Get your API key

2. Send your first check

3. Read the response

4. Wire it into signup