Didit AML Screening API

Didit AML Screening API

Overview

Screens a person or company against 1,300+ global watchlists and databases in one synchronous call. Two scores per hit: Match Score (is this the same person?) and Risk Score (how risky is the matched entity?).

Key constraints:

• full_name is the only required field (at least 2 characters).
• entity_type: "person" (default) or "company".
• nationality is an ISO 3166-1 alpha-2 code (ES, not ESP). Anything else returns 400.
• aml_name_weight + aml_dob_weight + aml_country_weight must sum to exactly 100.
• aml_score_approve_threshold must be <= aml_score_review_threshold.
• include_ongoing_monitoring: true requires save_api_request: true (the default).
• include_adverse_media: true waits for adverse media (about 5 s plus up to 25 s): use a client timeout of at least 60 seconds.
• Send an Idempotency-Key header when retrying, so a timeout never runs or bills a second screening.

Coverage (per the docs): sanctions (e.g. OFAC SDN, UN, EU, HM Treasury), law-enforcement and most-wanted lists (e.g. FBI, Interpol), PEPs (Levels 1-4) and their relatives and close associates, warnings and regulatory enforcement, fitness and probity, insolvency, and adverse media from 50k+ news sources (only with include_adverse_media: true).

Scoring:

1. Match Score (0-100) per hit: below aml_match_score_threshold (default 93) the hit is "False Positive", at or above it is "Unreviewed". Hits below 75 are not returned.
2. Risk Score (0-100) per hit: the highest risk score among non-False-Positive hits becomes aml.score, which sets aml.status through your two thresholds.

Persistence: with save_api_request: true (default) the screening is stored as a session: request_id works with GET /v3/session/{sessionId}/decision/, it shows in the Business Console, a status.updated webhook fires, and hits can be reviewed later. With false nothing is stored and request_id is only a correlation id.

Sandbox: sandbox API keys skip screening and billing and return a mocked result: "Approved" with zero hits unless you pass sandbox_scenario (decline_aml_hit returns one hit and "Declined", review_aml_possible_match returns "In Review"; catalog at GET /v1/sandbox/scenarios/). sandbox_scenario is rejected on live applications.

Pricing: AML Screening $0.20 per screening (one credit charged after a successful screening; idempotent replays are not charged again; standalone calls have no free tier). AML Monitoring $0.07 per monitored profile per year. These are the list prices until 1 November 2026, when Didit pricing changes and the 500 free checks a month become $10 of free credit a month. Check didit.me/pricing for current prices.

API Reference: https://docs.didit.me/standalone-apis/aml-screening Feature Guide: https://docs.didit.me/core-technology/aml-screening/overview Match Score: https://docs.didit.me/core-technology/aml-screening/aml-match-score Risk Score: https://docs.didit.me/core-technology/aml-screening/aml-risk-score

Authentication

Every request needs the x-api-key header. Use your application's API key from the Didit Business Console under Developers > API keys, or create an account and key programmatically (see Getting Started). Named keys with custom access need Sessions write to run standalone checks; a key limited to some workflows or to approved sessions cannot run them.

Getting Started (No Account Yet?)