Documentation

Risk signals in three endpoints.

Use FRDDB from your backend. Authenticate with an FRDDB API key, pin behavior with FRDDB-Version, and keep raw user decisions in your own product.

Base URL

https://api.frddb.com

Local API development usually runs at http://localhost:8787.

Send Authorization: Bearer frddb_live_.... API keys have explicit scopes: lookup, report, and admin.

Pass FRDDB-Version: 2026-05-06. FRDDB versions behavior with dated headers, not URL prefixes.

Check risk, report abuse, and send outcome feedback with cURL.

Requests, responses, scopes, and idempotency rules.

Error shape, status codes, rate limits, and write retry behavior.

Email HMAC identity, encrypted notes, audit logs, and no public search.

Data model

/check reads subject risk summaries, not raw reports. Reports and outcomes update the summary model so lookup latency stays boring.

organizations api_keys subjects reports report_outcomes subject_risk_summaries lookups audit_logs