Sample response

Review-friendly sanctions screening responses.

Veridex responses are designed to support reviewer workflows with a decision, score, explanations, match details, list metadata, timing, and a call ID when available.

Get API keyTry sandbox search

Example response shown for illustration. Actual fields, list counts, latency, and match details vary by request, selected lists, and current list availability.

What to store

Persist the call_id, status, decision, score, and top match details in your customer, payment, or case-management workflow.

What to show ops

Use summary, suggested_action, and explanations to give reviewers enough context without reading raw sanctions list entries first.

Example HIT response

{
  "call_id": "call_9fKx2q8QpL",
  "status": "HIT",
  "decision": "escalate",
  "risk_level": "high",
  "score": 96.4,
  "confidence_score": 96.4,
  "suggested_action": "Block or escalate for compliance review before proceeding.",
  "summary": "Likely match on OFAC_SDN for IVANOV, Viktor.",
  "explanations": [
    "High-confidence fuzzy match against a sanctions record.",
    "Top source list: OFAC_SDN.",
    "Program context: E.O. 14024."
  ],
  "matches": [
    {
      "list_name": "OFAC_SDN",
      "uid": "SDN-18874",
      "matched_name": "Viktor Ivanov",
      "primary_name": "IVANOV, Viktor",
      "score": 96.4,
      "entity_type": "individual",
      "dob": "1971-03-14",
      "program": "E.O. 14024"
    }
  ],
  "lists_checked": 3,
  "response_ms": 47,
  "screened_at": "2026-03-29T14:22:01Z"
}