POST/api/org/screening/screen
Request · use your organisation's API key
curl https://chainevidence.net/api/org/screening/screen \
-H "Authorization: Bearer $CE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"address": "0x7f9a00000000000000000000000000000000c214",
"chain": "ETH"
}'
Illustrative response · selected fields
{
"data": {
"verdict": "REVIEW",
"score": 32,
"sanctioned": false,
"matchedLists": [],
"riskTypologies": [
{
"code": "SCAM_REPORTED",
"severity": "high",
"label": "Reported scam address",
"source": "ScamSniffer"
}
],
"skippedChecks": [
"evm_outflows"
]
},
"meta": {
"requestId": "req_example"
}
}
A useful response schema
The data object contains the persisted screening result: verdict, score, matchedLists, breakdown, riskTypologies, sanctionsSnapshot and skippedChecks. The meta object includes a request ID and billing fields.
Limits depend on the endpoint
POST /api/org/screening/screen/batch accepts up to 1,000 items. The portal screening batch also accepts 1,000. POST /api/v1/sanctions/check accepts up to 100 addresses.
Signed event delivery
Screening and monitoring events can be delivered to registered webhooks with HMAC signatures. Verify the signature before your system acts on the payload.
The sample values are illustrative, not a result for the displayed address. The actual response also includes record identifiers, timestamps, list-state metadata and billing fields.