Products

AML Screening

Copy page

Screen individuals against global sanctions lists, PEP registries, and adverse media databases. The Dossiers API provides three complementary endpoints:

• Screening Requests — Submit an individual for asynchronous background screening and ongoing monitoring. Matches create Screening Alerts for your compliance team to review.
• Sanctions Search — Search global sanctions lists directly by name, country, or ID number. Returns matching sanction list entries in real time.
• PEP & High-Risk Search — Search for Politically Exposed Persons and high-risk individuals by name. Returns detailed dossiers with risk scores in real time.

---

Screening Requests

Creating a Request

Costs 10 credits per request.

Submit a POST /screening/request with the individual's name and optional details:

Code
curl -X POST https://api.dossiers.wiki/screening/request \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fullName": "John Smith",
    "dateOfBirth": "1985-03-15",
    "country": "LK",
    "externalId": "CUST-12345",
    "identificationDocument": {
      "type": "passport",
      "number": "N1234567",
      "country": "LK"
    }
  }'

Request Fields

Field	Required	Description
fullName	Yes	Full name of the individual to screen
externalId	No	Your own reference ID (e.g. customer ID, case number) for correlating results with your systems
dateOfBirth	No	Date of birth in YYYY-MM-DD format
country	No	ISO 3166-1 alpha-2 country code
identificationDocument	No	ID document details (type, number, optional country) to improve match accuracy

Providing additional details like dateOfBirth, country, and identificationDocument helps the screening engine reduce false positives.

Response

Code
{
  "requestId": "65f3c1a2b4e5f60012345678"
}

The requestId identifies the screening request. Screening runs asynchronously — when processing completes, you'll receive webhook events and any matches will appear as Screening Alerts in the Dossiers Dashboard.

Screening Workflow

1. Request created — amlScreening.screeningRequest.created webhook fires
2. Request queued — Checked against sanctions lists, PEP registries, and adverse media
3. Request completed — amlScreening.screeningRequest.completed webhook fires
4. Alerts triggered — If matches are found, amlScreening.screeningAlert.triggered fires for each alert

Data Sources

The screening engine checks against:

Source	Coverage
OFAC	U.S. Office of Foreign Assets Control sanctions
UN	United Nations Security Council consolidated list
FCDO	UK Foreign, Commonwealth & Development Office sanctions
DFAT	Australian Department of Foreign Affairs and Trade sanctions
CASL	Canadian Autonomous Sanctions List
INTERPOL	International Criminal Police Organization notices
PEP Registries	Politically Exposed Persons databases
Adverse Media	News and media sources flagging financial crime, corruption, etc.

---

Screening Alerts

A positive match raises a screening alert, delivered to you on the amlScreening.screeningAlert.triggered webhook and reviewed in your Dossiers Dashboard. The webhook payload carries the alert id used below.

Deleting an Alert

Code
curl -X DELETE https://api.dossiers.wiki/screening/alert/65f3c1a2b4e5f60012345679 \
  -H "Authorization: Bearer YOUR_API_KEY"

Code
{
  "alertId": "65f3c1a2b4e5f60012345679",
  "deleted": true
}

Free — this endpoint consumes no credits.

This deletes the screening behind the alert, not just the finding. Going with the alert are the screening request it was raised for, any other alerts raised from that same request, and every comment on them. That is deliberate: an alert is a verdict about a screening, so keeping the request while dropping the alert would turn "this name matched a sanctions list" into "this name was screened and matched nothing" — a materially different compliance record.

If you want to keep the screening on file and only discard the finding, mark the matches as false positives in the dashboard instead of deleting.

Deletion is immediate and irreversible, with no copy to restore from. An amlScreening.screeningAlert.deleted webhook fires once it is done, and a second delete of the same id returns 404.

Status	Meaning
200	Deleted, along with everything raised with it
401	Missing or invalid API key
403	API key has no AML Screening product access
404	No such alert in your organization — a wrong id, or already deleted

Alerts your organization still holds are also deleted automatically once they pass your data retention window.

Sanctions Search

Searching Sanctions Lists

Costs 5 credits per request.

Search directly against the consolidated sanctions data using POST /sanctions/search:

Code
curl -X POST https://api.dossiers.wiki/sanctions/search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fullName": "John Smith",
    "sources": ["ofac", "un"],
    "countries": ["LK"]
  }'

Request Fields

Field	Required	Description
fullName	No*	Full name of the individual to search for
idNumbers	No*	Identification document numbers to search for (matched independently of the name)
sources	No	Restrict the search to specific sanction sources (e.g. ofac, un)
countries	No	Restrict matches to specific countries

*Provide at least a fullName or idNumbers.

Response

Returns totalHits, the parsed searchingFor terms, and an array of matching sanction list documents, each describing the listed individual and the source list it appears on.

---

PEP & High-Risk Individual Search

Searching for Individuals

Costs 3 credits per request.

Search for PEPs and high-risk individuals by name using POST /high-risk/search:

Code
curl -X POST https://api.dossiers.wiki/high-risk/search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fullName": "John Smith"
  }'

Request Fields

Field	Required	Description
fullName	Yes	Full name of the individual to search for

Every API search runs fresh against all data sources and returns high-risk profiles only.

Response

Returns an array of IndividualDossier objects. Each dossier contains:

Code
{
  "id": "dossier_abc123",
  "fullName": "John A. Smith",
  "tagline": "Former Minister of Finance, Sri Lanka",
  "countries": ["LK"],
  "otherNames": ["J. A. Smith", "Johnathan Smith"],
  "dateOfBirth": ["1955-08-20"],
  "locations": ["Colombo, Sri Lanka"],
  "keywords": ["pep", "government-official"],
  "individualSummary": "Senior government official who served as...",
  "positionsHeld": [
    {
      "position": "Minister of Finance",
      "organization": "Government of Sri Lanka",
      "period": "2010–2015"
    }
  ],
  "closeAssociatesOrFamilyMembers": [
    {
      "name": "Jane Smith",
      "relationship": "spouse"
    }
  ],
  "identificationDocuments": [
    {
      "type": "passport",
      "number": "N1234567"
    }
  ],
  "riskScorecard": {
    "overallRiskScore": 0.72,
    "riskCategory": "high",
    "riskReasoning": "Individual held senior government position...",
    "pepScorecard": {
      "pepLikelihoodScore": 0.85,
      "category": "Senior Government Official",
      "reasoningSteps": [
        "Identified as former Minister of Finance",
        "Held position within the last 10 years"
      ]
    }
  },
  "cachedResult": false,
  "createdAt": "2026-03-05T11:35:06.000Z"
}

Risk Scorecard

Each dossier includes an AI-generated risk scorecard:

Field	Description
overallRiskScore	Risk score from 0.0 (low risk) to 1.0 (high risk)
riskCategory	Classification: "high", "medium", or "low"
riskReasoning	Narrative explanation of the risk assessment
pepScorecard.pepLikelihoodScore	PEP likelihood from 0.0 to 1.0
pepScorecard.category	PEP category (e.g. "Head of State", "Senior Government Official")
pepScorecard.reasoningSteps	Step-by-step reasoning for the PEP score

---

Webhook Events

Screening Request Events

Event	When it fires
amlScreening.screeningRequest.created	Fires immediately when a new screening request is submitted. Use this to confirm receipt and track processing in your system
amlScreening.screeningRequest.completed	Fires when the screening engine has finished processing the request against all data sources. Check for associated alerts after receiving this event

Example: amlScreening.screeningRequest.completed payload

Code
{
  "id": "evt_1717430820000_a1b2c3d4e5f60718",
  "type": "amlScreening.screeningRequest.completed",
  "organizationId": "org_...",
  "eventTriggeredAt": "2026-03-05T11:35:06.000Z",
  "data": {
    "alertCount": 1,
    "screeningRequest": {
      "id": "65f3c1a2b4e5f60012345678",
      "fullName": "John Smith",
      "externalId": "CUST-12345"
    }
  }
}

Screening Alert Events

Event	When it fires
amlScreening.screeningAlert.triggered	Fires when a positive match is found against sanctions lists or high-risk individual dossiers. An alert is only triggered when at least one match is not marked as a false positive. The payload includes the full alert with all matches and scoring criteria
amlScreening.screeningAlert.statusChanged	Fires when an alert's status transitions between TRIGGERED, INVESTIGATING, DISMISSED, or ACTIONED. Use this to sync alert status with your compliance workflow
amlScreening.screeningAlert.commentAdded	Fires when a compliance team member adds a comment to an alert. Useful for audit trail integration
amlScreening.screeningAlert.commentUpdated	Fires when a comment on an alert is edited
amlScreening.screeningAlert.commentDeleted	Fires when a comment is removed from an alert
amlScreening.screeningAlert.deleted	Fires when an alert is permanently deleted

Example: amlScreening.screeningAlert.triggered payload

Code
{
  "id": "evt_1717430825000_b2c3d4e5f6071829",
  "type": "amlScreening.screeningAlert.triggered",
  "organizationId": "org_...",
  "eventTriggeredAt": "2026-03-05T11:35:12.000Z",
  "data": {
    "id": "65f3c1a2b4e5f60012345679",
    "screeningRequest": "65f3c1a2b4e5f60012345678",
    "screeningAlert": {
      "status": "TRIGGERED",
      "dossiers": [
        {
          "id": "match_abc123",
          "scoring": {
            "nameMatch": { "aggregateScore": 0.92, "nameCommonalityScore": 0.45 },
            "idDocMatch": true,
            "dobMatch": { "exactMatch": true, "approxAgeDelta": 0 },
            "countryMatch": true,
            "matchConfidence": 0.88,
            "reasoning": "Strong name match with exact DOB and country match"
          },
          "markedFalsePositive": false,
          "result": { "fullName": "John A. Smith", "riskCategory": "high" }
        }
      ],
      "watchlistMatches": []
    }
  }
}

Alert Match Scoring

Each match (dossier or watchlist) includes a scoring object with the criteria used to evaluate the match:

Field	Description
nameMatch.aggregateScore	Overall name similarity score (0.0–1.0)
nameMatch.abbreviatedMatch	Whether the match was based on an abbreviated name
nameMatch.nameCommonalityScore	How common the name is (higher = more common, so less distinctive)
idDocMatch	Whether the identification document matched
dobMatch.exactMatch	Whether the date of birth matched exactly
dobMatch.approxAgeDelta	Approximate age difference in years
countryMatch	Whether the country matched
matchConfidence	Overall confidence score for the match (0.0–1.0)
reasoning	AI-generated explanation of why this was flagged as a match

Alert Lifecycle

Alerts move through these statuses as your compliance team reviews them:

Status	Meaning
TRIGGERED	New match found, pending review
INVESTIGATING	Compliance team is actively reviewing the alert
DISMISSED	Alert reviewed and determined to be a false positive or non-issue
ACTIONED	Alert confirmed and appropriate action has been taken

See the Webhooks guide for setup and signature verification details.