dateTimeValue value does not respect '1990-11-20' format in OpenAPI spec

We have encountered an case that dataTimeValue returns '1981' which does not respect the format of '1990-11-20' in the API spec.
Unforunately we could not parse the value with Java java.time.LocalDate. Any idea to rectify this?
GET url:
https://api-worldcheck.refinitiv.com/v2/cases/5jb79kta3sjt1fn96es1pvsap
JSON response:
{
"caseId": "330623198108066416",
"name": "<retracted>",
"providerTypes": [
"WATCHLIST"
],
"customFields": [],
"secondaryFields": [
{
"typeId": "SFCT_1",
"value": "MALE",
"dateTimeValue": null
},
{
"typeId": "SFCT_2",
"value": null,
"dateTimeValue": "1981"
},
Best Answer
-
@cliff.lee
When we screen a cases using secondaryFields
[{ "typeId": "SFCT_2", "dateTimeValue": "1990-11-20 " }] in the payload.
Which means that the matches with OR without the dateTimeValue as '1990-11-20 ' would be the same as the matches are populated due to entity name(primary fields) match alone while the secondary fields(dateTimeValue) decide whether it can be auto resolved by the system or unresolved for the user to find out if it is a MATCH or not. So, only auto resolved matches in a case would change because of it.If the match found has the same DOB the match will be marked as unresolved, other wise the match will be auto resolved as DOB provided does not match the profile in our DB.
Please find the JSON of a case with screened name "putin" and DOB as "1990-11-20"
"results": [{
"resultId": "5jb828qjzrlm1fo8y98s1p98v",
"referenceId": "e_tr_wci_1724038",
"matchStrength": "STRONG",
"matchedTerm": "ПУТИН,Андрей",
"submittedTerm": "putin",
"matchedNameType": "NATIVE_AKA",
"secondaryFieldResults": [
{
"field": {
"typeId": "SFCT_2",
"value": null,
"dateTimeValue": "1979-01-17" #DOB available in the WC DB for the particular match
},
"typeId": "SFCT_2",
"submittedValue": null,
"submittedDateTimeValue": "1990-11-20", #Submitted DOB
"matchedValue": null,
"matchedDateTimeValue": "1979-01-17",
"fieldResult": "NOT_MATCHED"
}]
Moreover, coming back to your query, we would suggest you to code it in such a way that your code accepts even if just YYYY is sent back (i.e. cover all possible combinations). Response handling should take care of these scenarios where only YYYY is returned when your parse YYYY-MM-DD.
0
Answers
-
@cliff.lee
Thanks for your query!
You can pass the DOB values in 3 possible formats YYYY-MM-DD, YYYY-MM and even just YYYY. So, basically if you are passing the value i.e. YYYY-MM-DD and getting the response back as YYYY, it's expected behavior.
Kindly get back to us if you have any additional questions. And also we would like you to share the complete request body in case you need further assistance.0 -
Got it. However, the Java API could not handle this when parsing response JSON at first place. Is it possible to return the day and month portion as well?
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.5K 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
- 560 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
- 725 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 中文论坛