Quickstart

Make the first lookup from your backend.

FRDDB is server-to-server. Keep API keys off browsers, pin the API date, and send outcome feedback when a case resolves.

Check an email risk signal

Call /check during signup, checkout, refund, or manual support review.

POST /check

curl https://api.frddb.com/check \
  -H "Authorization: Bearer frddb_live_..." \
  -H "Content-Type: application/json" \
  -H "FRDDB-Version: 2026-05-06" \
  -d '{"email":"buyer@example.com","context":{"event":"signup"}}'

Report verified abuse

Reports require authenticated organizations and evidence metadata. Use idempotency keys for safe retries.

POST /reports

curl https://api.frddb.com/reports \
  -H "Authorization: Bearer frddb_live_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: dp_123" \
  -H "FRDDB-Version: 2026-05-06" \
  -d '{
    "email":"buyer@example.com",
    "category":"chargeback",
    "occurred_at":"2026-05-04T12:00:00Z",
    "amount":9900,
    "currency":"USD",
    "evidence_type":"stripe_dispute",
    "external_case_id":"dp_123",
    "notes":"Dispute filed after successful service usage."
  }'

Feed outcomes back

Outcome feedback keeps the risk graph from going stale. Without feedback, every risk database slowly becomes nonsense.

POST /outcomes

curl https://api.frddb.com/outcomes \
  -H "Authorization: Bearer frddb_live_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: outcome_123" \
  -H "FRDDB-Version: 2026-05-06" \
  -d '{
    "report_id":"rep_123",
    "outcome_type":"dispute_lost",
    "occurred_at":"2026-05-06T12:00:00Z",
    "metadata":{"processor":"stripe"}
  }'