Integration with world check one api

In my application I have to screen a party and get the result and based on that we will activate the party. So I am following these steps.
1. Get groupId and store for all future screening request. (one time)
2. Get Case System Id for a Customer (cases) (one time and store in customer master) and for future screening request I am taking the same case system Id from the Customer master. Is this a good method or do I need to generate case system id every time?
3. Screen Case (screeningRequest)
4. Get Result (results)
is this process ok? or is there a better way ?
thanks
Best Answer
-
I have already shared a link with you that mentions the correct steps to screen a case and then check the world check profile.
I am sharing it again here:
I am rewriting the same content (as in the above link) for your reference:
1. Get top level groups: One time, if you are planning on to make changes in the group structure using the WC1 GUI.
2. Get the case template of the group: One time, if you are planning on to make changes in the case template using the WC1 GUI.
3. Get the country ISO list: One time. But the information is subjected to change so we recommend them fired periodically.
4. Get Case System Id for a Customer (cases) (one time and store in customer master) and for future screening request I am taking the same case system Id from the Customer master. Few questions here:
Are you saving a case here? or just pulling the case system Id of the already screened case or saved case?
Is this a good method or do I need to generate case system id every time?
[Ans by Irfan]: This depends on what are you trying to do. If you want to re screen an existing client, then using the same case system Id is a good idea. If you are screening a new client whose name is same that exists in your screened case DB already but the secondary identifier like place of birth, date of birth, etc is different, I would suggest you to create a new case, meaning generate a new case system Id for it.
In short, if you are re screening existing clients, use the same case system Id.
If you are screening a new client even though a file with same name exists (provided they are two different clients), generating a new case system Id is a better Id. This will lead to better tracking and visibility on each client you have screened.
5. Screen a case
6. Audit API: This is to find if the case has been screened or not.
7. Get screening results (If the case is screened,i.e, yes for step 6 and still there is an empty response for this API, that means the case has not results. This is why audit API is important).
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 697 Datastream
- 1.5K DSS
- 632 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
- 256 ETA
- 563 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
- 749 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
- 123 Open DACS
- 1.1K RFA
- 107 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 中文论坛