Questions Regarding World Check One

Hello,
I have a few questions about the World Check One service.
- Is there a way to configure the name match threshold via the API, per screening request?
- Do secondary fields (ie. DOB and location) have any effect on the match-strength of a result or on which entities are matched in a search?
- We need to obtain information about associates, AKAs, all PEP roles and whether the match is deceased, for each match identified in a search - do you offer any way to do this other than to send requests to the below endpoints for each match?
/reference/records/{id}
/reference/records/{id}/pep
4. In the same way as the above, we need to capture adverse media information for each match in a search - does the MediaCheck service provide the ability to retrieve adverse media articles for a specific match?
Best Answer
-
Hi @mark06
1. Yes, we do have a way so that you can configure the "Name Match Threshold"
Login to WC1 UI => Groups => WORLD-CHECK SETTINGS => Configure Name Matching Threshold.
2. Secondary fields doesn't have any impact on the "matchStrength" of the results, however, it will give you the granular view as whether the secondary fields which you had added as part of request are matching with the WC records or not (If YES, then fieldResult will be "Matched" otherwise it will show as "UNKNOWN" "NOT MATCHED")
3. Unfortunately, there is no other way to get the WC records (via the API) except below API endpoints.- /reference/records/{id}
- /reference/records/{id}/pep
4. You can utilize the "SEQ-case-mediacheck-article-content: Work with single MediaCheck article content" API endpoint to get the desired details.
Please feel free to reach out to us if you have any additional questions.
Thanks
Vivek Kumar Singh
0
Answers
-
Hi @mark06
Thanks for your query!
Please allow us to review the details, will get back to you shortly.Thanks
Vivek Kumar Singh0 -
Hi Vivek,
Thanks for your reply. Considering the information that we require and your answer to #3, could you confirm that you support the following sequence - particularly with regard to the number and frequency of requests:First:
/cases/screeningRequest
then, immediately after, for each matched entity:
/reference/records/{id}
and
/reference/records/{id}/pep
Thanks0 -
@mark06Hi
Thanks for your query.Endpoint sequence depends on the use case, however, your sequence of API calls are optimal.
Thanks
Vivek Kumar Singh
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛