Integrate Refinitiv World-Check One API for PEP and sanctions screening with risk-based filtering by risk entity category

domain: developers.lseg.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Authenticate using HMAC-SHA256 signed request headers — compute the signature over the HTTP method, Content-Type, date, and request path
  2. POST to /v2/cases/screeningRequest with a CaseSystemId, secondaryFields (dateOfBirth, nationality), and a groupId corresponding to your screening configuration
  3. Poll GET /v2/cases/{caseSystemId}/results or handle the webhook callback to retrieve the screened result
  4. Filter results by the entityType and primaryName fields; use the category field to separate PEP hits from sanctions hits
  5. For each ongoing customer relationship, resubmit a screening request at the interval required by your AML policy (typically monthly or on trigger events)

Known gotchas

Related routes

Screen a customer or counterparty against consolidated sanctions and PEP data using the OpenSanctions match API
opensanctions.org · 5 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans