Management API examples use
$CLAUSUM_API_BASE with a dashboard session JWT. The hostname is assigned by Clausum support — see Access & environments.Entry types
list_type | Matches against |
|---|---|
email | Exact email address |
email_domain | Email domain (e.g. example.com) |
ip_address | Single IP |
ip_range | CIDR range |
device_fingerprint | Device fingerprint |
card_bin | First 6 digits of the card |
card_hash | Hashed card number |
country | ISO country code |
phone | Phone number |
customer_id | Your internal customer id |
Severity
| Severity | Effect on assessment |
|---|---|
block | Hard-declines the transaction (risk_score = 100) |
flag | Adds significant weight |
review | Adds moderate weight, routes to review |
Managing entries
Blocklist endpoints are part of the management surface and use a dashboard session JWT.Adding entries requires the
admin, analyst, or compliance_officer role. Deleting entries requires admin.Automatic population
You usually don’t add entries by hand. When you callreport-fraud, Clausum automatically blocklists the offending email (block), card BIN (flag, for card testing / friendly fraud), and IP (block) — each tagged with source: "fraud_report" and linked to the generated case.
Expiring entries
Setexpires_at to a timestamp to auto-deactivate temporary blocks (for example a 24-hour velocity ban). Omit it for permanent entries.
Normalization
Clausum normalizes values on write:email / email_domain are lowercased and country codes are uppercased. Duplicate entries (same org + type + value) return 409 Conflict.