WorldCheck One API: about specific categories and further information in /v1/reference/profile en...

...dpoint
I have some doubts about how I can obtain data from World-Check API regarding an individual, those data should help me to block access to our investment platform or if we finally let it operate.
As you know, when a synchronous screening is performed, Wold-Check sends a series of results in an array called results (if there are no results, well, nothing to worry about).
Within each item of the results array there is a tag called categories that can list the different situations in which the subject is classified.
I have requested access to the complete documentation to see them all, but I think they are the following:
- Sanctions
- PEP (Political Exposed Person)
- Law Enforcement
- Regulatory Enforcement
- Other Bodies
Well, it turns out that although some cases are clear, others do not know if we should prevent access to the subject. That is why it is necessary to know what data I should look at.
For example, if the label is:
- Sanctions: access is not allowed, it is blocked in our platform. Crystal clear.
- PEP: access is allowed.
- Law enforcement: if individual is wanted by the Police then individual is not allowed access, in other cases access is granted. This point is not clear. Where can I take a look at to differentiate options?
- Regulatory enforcement, should not be a reason for blocking, access granted.
- Other bodies, depending on the case is blocked or not, for example if individual is Russian.
As you can see, the Law Enforcement and Other Bodies cases have gray areas and I don't know what data I should take a look to decide if they are denied accessing to our platform.
I know that there is an endpoint that allows you to collect the complete profile given a result (using the referenceId) but I do not know what data of the response of / v1 / reference / profile I have to set in order to determine whether we give access or not.
Can you help me on this and point where I can take a look (I think it is in the World-Check's /v1/reference/profile endpoint but what labels)
Regards, and thank you very much.
Best Answer
-
Hello @jjcermeno,
Sorry for the late response. Actually thats a really good and complex question that I would like to explain it for you.
First of all we can't give you a straight answer about how you should treat each entity you screen. I will try to cover each uncertainty that you highlighted.
Let's take an example for name Jafar MOHAMMADI. It's straightly up to you business profile. For exact match on Jafar you get:
"categories": [
"PEP",
"Other Bodies",
"Other Bodies",
"Sanctions",
"Regulatory Enforcement"
],This way going only with one category would not work for your application logic.
If you go into the details you might find factors that might decide if its DNDB profile or not.
I would suggest you to use SEQ-case-investigate-world-check-profile: Get a World-Check profile for each profile you are interested in and look at "detailType": "REPORTS" that might give you some wider look at the entities you are screening.
I hope that it helps you a bit with your problem.
0
Answers
-
Thank you very much, Michal, for your response.
I was suspecting that categories, category and details are important. However, while details is text content, categories and category seems to provide predefined values and I would like know all possible values and related fields but the Quickt Start Guide does not mention that. I asked access to full documention (I work for a company that is currently a customer) and despite following the instructions, I still have not access to it. Do you think you can help getting full documentation?
Thank you very much for your help.
0 -
@jjcermeno Can you please confirm your WC1 API account so that I can give you access to the documentation?
0 -
Don't you think It's a little bit weird to be asked for my WC1 account when you can send me an email asking the same. I am not going to answer to that publicly. Sorry for the inconveniences.
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 中文论坛