Ingest risk signal
Submit a risk signal for a specific entity. Risk signals are scored observations from fraud-detection sources such as device fingerprinting, IP reputation services, email verification providers, or your own internal rules engine.
Each signal is stored with full tenant isolation (row-level security) and can be used to inform downstream risk decisions.
Signal sources
Signals must specify one of the following sources:Subject types
Each signal must reference a subject. Supported types:Risk score
Therisk_score field is an integer between 0 and 100:
- 0 — no risk detected
- 50 — moderate risk
- 80+ — triggers automatic review decisions
- 100 — highest risk
Idempotency
Include anIdempotency-Key header (UUID) to prevent duplicate signals during retries. If you send the same key twice, the duplicate is silently ignored.Authorizations
API key for machine-to-machine authentication
Body
Origin of the signal (e.g. device_fingerprint, ip_reputation, email_verification, document_analysis, behavioral)
"device_fingerprint"
Classification of the risk signal
"velocity_anomaly"
Risk score between 0 (no risk) and 1 (highest risk)
0 <= x <= 10.85
The type of entity this signal relates to
user, device, ip, document, session "user"
Identifier of the entity being evaluated
"usr_8f14e45f"
Arbitrary metadata to attach to the signal
Response
Risk signal ingested
Origin of the signal (e.g. device_fingerprint, ip_reputation, email_verification, document_analysis, behavioral)
"device_fingerprint"
Classification of the risk signal
"velocity_anomaly"
Risk score between 0 (no risk) and 1 (highest risk)
0 <= x <= 10.85
Arbitrary metadata associated with the signal
The type of entity this signal relates to
user, device, ip, document, session "user"
Identifier of the entity being evaluated
"usr_8f14e45f"

