Event types
The event_type values KaizoCore understands, and how they drive per-action thresholds.
Supported values
event_type | Typical use |
|---|---|
login | Account sign-in |
signup | Account creation |
checkout | Cart-to-order submission |
payment | Payment-method submission specifically, if distinct from checkout in your flow |
search | High-volume, low-stakes lookups — often scraped, rarely fraud-critical |
event_type is optional on the request, but supplying it unlocks
per-action thresholds: your account can configure a different
block/challenge score boundary for each event type, since the right
tolerance for a search endpoint is very different from the right
tolerance for payment. A default, sensible set of thresholds ships with
every account (tighter for payment and checkout, looser for search), and
you can adjust them from the dashboard.
Why this exists as a layer on top of the score, not instead of it
The base 0–100 score is always computed the same way regardless of
event_type — it's a measure of how bot-like or fraud-like the request
looks, full stop. Per-action thresholds only change where the line is
drawn for turning that score into a decision, not how the score itself is
calculated. A borderline score might be ALLOW_WATCH on a search call and
SOFT_CHALLENGE on a payment call, using the exact same underlying
evidence, because the cost of a false negative is different for the two.