Thomson Reuters World‑Check API – Sanctions Screening & KYC API

Thomson Reuters API for AML, KYC, and Sanctions Screening

The Thomson Reuters API is commonly associated with World-Check screening workflows used for AML, KYC, sanctions, PEP, and adverse media checks. Today, this solution is offered under LSEG’s World-Check product family, including World-Check One API and related screening tools. These APIs help U.S. fintechs, banks, lenders, and compliance teams automate onboarding checks, reduce manual review effort, and support more consistent risk-screening workflows. 

What Is Thomson Reuters API in Compliance Workflows?

When many teams search for Thomson Reuters API, they are usually looking for the World-Check screening capability historically associated with Thomson Reuters and later Refinitiv. The current official product family is under LSEG Risk Intelligence, where World-Check One API is positioned as a REST/JSON screening API for onboarding, KYC, third-party due diligence, transaction screening, and ongoing monitoring.

For U.S. organizations, this matters because compliance teams need fast and defensible ways to screen customers, merchants, counterparties, and vendors against sanctions, politically exposed persons, enforcement exposure, and adverse media risk. LSEG states that its World-Check tools support these screening use cases and help reduce false positives through more structured workflows.

Why Businesses Use Thomson Reuters API

A modern Thomson Reuters API integration is useful when a business wants to:

• screen customers during onboarding

• review merchants or business owners during KYB

• check vendors and counterparties during due diligence

• support payment or transaction screening workflows

• maintain ongoing monitoring after the initial approval process

LSEG describes World-Check One API as supporting onboarding, KYC, third-party due diligence, transaction screening, and ongoing screening. It also supports synchronous or asynchronous screening with secondary identifiers such as date of birth, gender, and document details.

Key Use Cases for U.S. Fintech and Regulated Products

1. Customer Onboarding

Use the Thomson Reuters API to screen individuals or businesses before account creation, wallet activation, lending approval, or payments enablement.

2. Merchant and KYB Screening

Fintech platforms, payment processors, and embedded finance providers can screen beneficial owners, directors, and legal entities during onboarding and re-verification.

3. Third-Party Risk Reviews

Compliance teams can use the API to review suppliers, introducers, brokers, affiliates, and strategic partners.

4. Ongoing Monitoring

Instead of screening only once, businesses can trigger periodic re-screening or event-based monitoring as risk posture changes.

5. Transaction-Linked Screening

For some use cases, organizations may use API-driven screening in payment or case-creation workflows, depending on their operational model and product choice. LSEG also offers more real-time and stateless screening options in its current portfolio.

What Data Can Be Screened?

A Thomson Reuters API workflow is typically used to screen against categories such as:

• sanctions exposure

• PEP status

• adverse media

• law and regulatory enforcement information

• reputational risk indicators

• private or internal watchlists, depending on setup

LSEG’s product pages and quick-start materials describe screening across sanctions, PEPs, adverse media, enforcement data, and broader financial crime risk signals.

What the Thomson Reuters API Helps With

Technical Integration Overview

LSEG’s World-Check One API is described as a workflow-based REST/JSON web service over HTTPS. Documentation also notes that some World-Check APIs use API keys and HMAC-based message signatures for request authentication, depending on the product. 

Common integration flow

1. Collect customer or business identity data

2. Send screening request through the Thomson Reuters API

3. Receive potential match results

4. Apply internal scoring or review rules

5. Create or update a compliance case

6. Trigger analyst review if needed

7. Store audit logs and screening outcomes

curl --request POST "https://api.example-screening.com/v1/cases/screeningRequest" \
  --header "Content-Type: application/json" \
  --header "Authorization: Signature <your-signed-header>" \
  --data '{
    "entityType": "INDIVIDUAL",
    "name": "Jane Doe",
    "secondaryFields": {
      "dateOfBirth": "1991-07-15",
      "country": "US"
    },
    "groupId": "your-group-id",
    "caseSystemId": "cust_102948"
  }'

Example response structure

{
  "caseId": "case_987654",
  "status": "PENDING_REVIEW",
  "matches": [
    {
      "matchScore": 92,
      "riskCategory": "PEP",
      "recordId": "wc_12345"
    }
  ]
}

This code is an illustrative example, not an official LSEG sample. Use the official developer portal for exact endpoints, authentication, and payload requirements. Official materials confirm REST/JSON patterns, HTTPS delivery, and developer onboarding resources. 

Best Practices for Thomson Reuters API Implementation

Normalize your screening layer

Do not connect every frontend flow directly to the screening provider. Build an internal compliance service layer that handles retries, logging, mapping, and review-state management.

Use secondary identifiers

Screening is stronger when names are combined with date of birth, geography, or document-related fields. LSEG documentation explicitly notes support for secondary identifiers.

Design for false-positive handling

A good compliance workflow is not only about generating hits. It also needs clear review queues, analyst notes, decision logging, and escalation paths.

Plan for monitoring

Initial onboarding checks are not enough for many regulated use cases. Ongoing screening can be important where counterparties, merchants, or customers remain active over time. LSEG states that ongoing screening is supported in its World-Check product set.

Keep auditability in mind

Your integration should capture request timing, inputs used, decision history, reviewer actions, and versioned rule logic.

Who Should Consider Thomson Reuters API Integration?

The Thomson Reuters API approach is relevant for:

• fintech apps

• digital banking platforms

• payments and merchant onboarding systems

• lending and credit platforms

• B2B marketplaces

• investment and wealth products

• corporate compliance teams

• vendor onboarding platforms

Any U.S. business dealing with identity verification, merchant onboarding, regulated payments, or counterparty risk can benefit from a more structured screening integration.

FAQ 

1. What is Thomson Reuters API?

The term Thomson Reuters API is often used to refer to the World-Check screening capability historically associated with Thomson Reuters. The current official product family is now under LSEG Risk Intelligence, including World-Check One API and related screening offerings.

2. What is Thomson Reuters API used for?

It is used for compliance-related screening such as AML, KYC, sanctions checks, PEP screening, adverse media review, third-party due diligence, and ongoing monitoring workflows.

3. Is Thomson Reuters API good for KYC and AML?

Yes. World-Check tools are designed to support customer screening, business screening, due diligence, and financial crime risk workflows. LSEG explicitly positions these solutions for KYC and AML use cases.

4. Does Thomson Reuters API support sanctions and PEP screening?

Yes. Official LSEG materials describe screening coverage for sanctions, politically exposed persons, adverse media, and enforcement-related risk categories.

5. Is Thomson Reuters API the same as World-Check One API?

In most practical search contexts, users looking for Thomson Reuters API are referring to World-Check-related screening products. The current official API branding is LSEG World-Check One API or other World-Check screening APIs, depending on the workflow.

6. What kind of authentication does Thomson Reuters API use?

Authentication depends on the product. LSEG documentation for World-Check APIs references API credentials and, in some cases, HMAC-based request signatures. Teams should verify the exact scheme in the official developer docs for their selected API.

7. Can Thomson Reuters API be used for ongoing monitoring?

Yes. LSEG states that World-Check One API supports ongoing screening capabilities in addition to onboarding and due diligence workflows.

8. Who should integrate Thomson Reuters API?

Banks, fintechs, lenders, payment companies, marketplaces, and regulated businesses that need customer, merchant, vendor, or transaction-related screening can consider this type of integration.