API - Trigger a Get results from WC-1

Hi all,
We are using the WC-1 API since few months. We work on some evolutions and I'm wondering if its possible to trigger a Get results when a case present a new match, and this match is Postive/High.
In others terms, actually the get results request is sent automatically from our SAP System and get executed only for the cases flagged as "Screening in progress" on the SAP side (Screening in progress : Case with at least one unresolved match).
However, once all the matchs of a case are resolved, the status SAP change to released or Restricted. But if a case flagged as "Released" or "Restricted and our Get results don't recover the results from this case . If a new match appears trough the OGS feature for this cases, We would like that WC-1 trigger a get results and send the results to SAP when this new match is resolved.
Thanks by advance for your answer.
Best Answer
-
Hi @nnn
Use the API call – “SEQ-case-monitor-ogs: Monitor ongoing screening updates on cases“ to check for the updates on the cases. Monitor OGS API call provides you the functionality to query in the update date. Every update that gets listed in the monitor OGS API response, there is respective update date mentioned against the casesystemId, so even if the same case has had multiple updates it will all show up and you can determine using the update date field in the response as to which update is the latest one.
When you use the API call – ‘Monitor OSG’ it provides the information in the below format –
"results": [
{
"providerType": null,
"caseSystemId": "0a3687cf-65b4-154b-9990-d45c0001251a",
"numberOfNewResults": 0,
"numberOfUpdatedResults": 1,
"updateDate": "2019-01-24T19:42:20.039Z" - //Date of update
}
]
You have to use the API call – ‘SEQ-case-investigate-results: Get screening results’ for the above case-system-id and check for 2 things –
- Modification date : Modification date for the profile under the results would be the same as the updateDate.
- Review required : The value of the reviewRequired would be True for the profile which has an update
{
"resultId": "0a3687d0-65b4-1d30-9990-d45d0026e785",
"referenceId": "e_tr_wci_1059690", \\ The world-check profile reference number.
"matchStrength": "WEAK",
"matchedTerm": "Pasa YASAR",
"submittedTerm": "FAYSAL YAŞAR",
"matchedNameType": "PRIMARY",
"secondaryFieldResults": [],
"sources": [
"b_trwc_PEP N"
],
"categories": [
"PEP"
],
"creationDate": "2018-10-05T08:21:43.855Z",
"modificationDate": "2019-01-24T19:42:19.736Z", \\ Modification date of the updated profile would be the same as the updateDate from the Monitor OGS
"resolution": null,
"resultReview": {
"reviewRequired": true,
"reviewRequiredDate": "2019-01-24T00:00:00.000Z",
"reviewRemark": null,
"reviewDate": null
}
},
The Next step would be to use the API call – ‘SEQ-case-investigate-world-check-profile: Get a World-Check profile’ to fetch the full details of the profile and check in the updatedDates for the date received in the Monitor OGS API call or the modificationDate from the Get screening results API call. Snippet below -.
"updatedDates": {
"ageUpdated": null,
"aliasesUpdated": null,
"alternativeSpellingUpdated": null,
"asOfDateUpdated": null,
"categoryUpdated": "2015-11-27T00:00:00Z",
"citizenshipsUpdated": null,
"companiesUpdated": "2015-11-27T00:00:00Z",
"deceasedUpdated": null,
"dobsUpdated": "2014-02-26T00:00:00Z",
"eiUpdated": null,
"enteredUpdated": null,
"externalSourcesUpdated": "2019-01-24T00:00:00Z",
"firstNameUpdated": null,
"foreignAliasUpdated": "2012-10-18T00:00:00Z",
"furtherInformationUpdated": "2019-01-24T00:00:00Z",
"idNumbersUpdated": null,
"keywordsUpdated": null,
"lastNameUpdated": null,
"linkedToUpdated": "2019-01-24T00:00:00Z",
"locationsUpdated": "2015-11-27T00:00:00Z",
"lowQualityAliasesUpdated": null,
"passportsUpdated": null,
"placeOfBirthUpdated": "2014-02-26T00:00:00Z",
"positionUpdated": "2015-11-27T00:00:00Z",
"ssnUpdated": null,
"subCategoryUpdated": "2015-11-27T00:00:00Z",
"titleUpdated": null,
"updatecategoryUpdated": "2019-01-24T00:00:00Z"
},
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 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
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 717 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
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛