Date of birth secondary field values must be a valid date not containing any time fields. These d...

...ates are not allowed to be in the future or more than 150 years in the past
Hi,
When i am creating a case or requesting a screen for test with these parameter, i am getting invalid date error. But i am passing date as per documentation DATE is a Date in ISO 8601 format excluding Week and Ordinal dates.
What is wrong or how can i fix it?
{
"secondaryFields": [{ "typeId":"SFCT_1", "value":"MALE" },
{ "typeId":"SFCT_2", "value":"2000-02-25" },
{ "typeId":"SFCT_3", "value":"IND" },
{ "typeId":"SFCT_4", "value":"IND" },
{ "typeId":"SFCT_5", "value":"IND" }],
"entityType": "INDIVIDUAL",
"customFields": [],
"groupId":"{{group-id}}",
"providerTypes": [
"WATCHLIST"
],
"name": "vishwanath kumar"
}
{
"error": "INVALID_DATE_OF_BIRTH",
"cause": "Date of birth secondary field values must be a valid date not containing any time fields. These dates are not allowed to be in the future or more than 150 years in the past."
}
Best Answer
-
Thank you for your query.
For the date field, the value has to be passed in dateTimeValue.
Can you please use the below format and it should work.
{
"typeId":"SFCT_2",
"dateTimeValue":"2000-02-25"
},Hope this helps.
0
Answers
-
Yes, it is working. i got it from i-am-building-application-to-create-cases-into-wor this question. Thanks for the help.
But i have one more question as i am screening a case i am getting more than one result. How can i identify which one is my result and also how this response is helping to verify a case background ?0 -
Yes, it is working. i got it from i-am-building-application-to-create-cases-into-wor this question. Thanks for the help.
But i have one more question as i am screening a case i am getting more than one result. How can i identify which one is my result and also how this response is helping to verify a case background ?
0 -
You can refer to the match strength against the submitted value and check further details to determine if the hit is your match or not.
If in case you are unable to identify the match with the information in the results, you may us the API call - 'Get a World-Check profile' to fetch full case of the profile and then determine the same based on your Business logic.
You may also refer to this query for reference.
0 -
Ok,
Thanks @Prabhjyot
0 -
Ok,
Thanks @Prabhjyot.Mandla
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
- 689 Datastream
- 1.4K DSS
- 625 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
- 558 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
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 277 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 1.9K Refinitiv Data Platform
- 696 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
- 94 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛