Profile details after case is created

Hello.
We have started implementing integration with your API and this integration requires us to have available some specific profile properties such as primaryName, birthDate, gender and locations and specific match information (referenceId, matchStrength, matchedTerm, ...)
When we first create the case for synchronous screening, via the POST /cases/screeningRequest endpoint, we receive all (profile and match) required information back for each of the matches found.
The problem for us happens afterwards. After revisiting the case, we use GET /cases/{caseSystemId} to retrieve the created case. This request's response includes partial information previously included about the profiles on the request above, such as referenceId, matchStrength and matchedTerm, but it doesn't include other crucial information for us, such as primaryName, birthDate or gender.
I understand that the only way of retrieving this additional information is through, then, performing an additional request for each one of the profiles to GET /reference/profile/{id}.
Is this correct or do we have a less intrusive way of retrieving these profiles information in batch or something similar? Is there a better workflow for retrieving the same information retrieved by the synchronous screening again?
Thank you
Best Answer
-
GET /cases/{caseSystemId} is an API call to fetch the case details only but not the match details of the case.
Please use the API call "SEQ-case-investigate-results: Get screening results" : GET cases/{{case-system-id}}/results to fetch the screening results of the case whose results you would like to view. Please be sure to use the correct case system Id to query the results.
When you request this API call, you may see less information that the endpoint "POST /cases/screeningRequest " but you should have most of the attributes you are looking for.
To fetch the complete profile of a match, there is no batch way of pulling all the WC profiles of all the matches of a case in a single API call. You will have to extract the referenceId of all the matches and repeatedly call the API "GET:reference/profile/{{worldcheck-profile-id}}" for each of the extracted referenceId/profile Id.
0
Answers
-
Thank you @Irfan.Khan. I can confirm we're actually using the GET cases/{{case-system-id}}/results to fetch the created case, my mistake on mentioning the other one...
Unfortunately, it doesn't have the information we require, so additional requests to the Profile API are needed, as you said.
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
- 748 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 中文论坛