How can i retrieve the World-Check profiles post screening in a best possible manner ? Are there ...

Best Answer
-
Scenario:
Ideally when you screen an entity you get X number of matches and our customers usually fetch the profiles of all the matches obtained in the result, for example: let’s say you screened John Smith and you obtained 90 matches against it in which 30 are strong/medium matches and 40 are weak matches and 20 are auto-resolved matches which can be ignored so consuming the “Get Profile API” for all the 90 matches would not only potentially cause unnecessary load on the World-Check Platform but also slow down the turnaround time on the customer end which is not at all efficient.
Best Practice Approach:
To overcome this, we recommend our customers to follow a set of best practices laid down to make the best use of our product which will help you build your integration in the most efficient manner.
what we recommend here is that when you place a screening request from your system and receive a list of matches in the response back from World-Check One, the profile API must be called only when the user clicks on the potential match on their surface and not for every match returned in the response, this way we avoid the large response time on the client’s system and also unnecessary potential load on our platform.
An important point to note here is that you can easily ignore the Auto-resolved matches while fetching the profiles as highlighted in the above scenario, out of the 90 matches 20 are auto-resolved so you can build logic in place at your end to ignore these 20 matches and then fetch profiles of the potential matches on trigger i.e. when a user clicks on any of the potential matches "Fetch World-Check Profile" API can be consumed for that particular match.
Suppose, John Smith has 230 matches, fetching 230 profiles is just inefficient way of consuming the Get Profile API, we must ensure the profile details are fetched only for the potential matches in interest and not for all the matches.
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
- 695 Datastream
- 1.5K DSS
- 631 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 562 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 736 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛