Submits a risk signal for a specific subject. Risk signals are scored observations from fraud-detection sources such as device fingerprinting, IP reputation services, email verification providers, or your own rules engine. Each signal is stored with full tenant isolation and can be used to inform downstream risk decisions. See the risk signals guide for integration details.Documentation Index
Fetch the complete documentation index at: https://docs.truthlocks.com/llms.txt
Use this file to discover all available pages before exploring further.
Signal sources
Signals must specify one of the following sources:| Source | Description |
|---|---|
verification | Signals from the verification pipeline |
login | Login-related fraud indicators |
attestation | Attestation-related signals |
external | Signals from third-party fraud providers |
manual | Manually reviewed or submitted signals |
Subject types
Each signal must reference a subject. Supported types:| Subject type | Use case |
|---|---|
user | Signals tied to a specific user account |
issuer | Signals related to an issuer entity |
attestation | Signals related to a specific attestation |
session | Session-level behavioral signals |
ip | IP-address-level signals |
device | Signals from device fingerprinting |
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.
