REFINITIV WC1 API - Possible Values in secondaryFieldResults \ fieldResult

Hello,
What are the possible values returned in the fieldResult
field by the Refinitiv API, and what does each value represent?
For example: MATCHED
, NOT_MATCHED
, etc.
Thank you in advance.
Answers
-
Hello @mibaraket - thank you for reaching out to us.
Can you please clarify what WC1 API endpoint you are using? I look forward to your response.
Best regards,
Judith
1 -
Hello,
I'am using WC1 API REFINITIV
Please find bellow un example of the filed :
Best Regards
0 -
Hello @judith.pillado01
Kind reminder,
Could you please assist me? I wasn’t able to find the information in the documentation, and I’m currently working under time constraints.Best Regards.
0 -
Hello @mibaraket
Thank you for your patience. I am assuming that you are referring to the v3 WC1 API endpoint: "Save and Screen a Case".
The possible values for "fieldResult" are "MATCHED" and "NOT_MATCHED". In my example below (similar to yours), I added a secondary identifier for gender:
It says "MATCHED" because the result given for the individual I screened matched based on the Secondary Identifier for gender (I screened using "MALE" as "SFCT_1 typeId"). It would say "NOT_MATCHED" if the result was an individual of a "FEMALE" gender.
Ultimately, the "fieldResult" will say "MATCHED" or "NOT_MATCHED" based on your value and result for the secondary identifier you chose when screening a case.
Please let me know if you have any further questions.
Best regards,
Judith
0 -
Hello @judith.pillado01
Thank you for your response and assistance.
I am working with version v2.44 of the WC1 API, specifically the
EQ-screen-sync-organisation: Perform Synchronous Screening: Organisation
endpoint.I have encountered an example with the value
UNKNOWN
, and I would like to know if there are any other possible values besidesMATCHED
,NOT_MATCHED
, andUNKNOWN
.Best regards,
0 -
Hello @mibaraket
Thank you for pointing this out. The "UNKNOWN" value appeared in this case because the registered country is unknown for that organisation. Asides from "MATCHED", "NOT_MATCHED", and "UNKNOWN", there are no other possible values for "fieldResult". Thanks.
Please let me know if you have any questions.
Best regards,
Judith
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
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 251 ETA
- 556 WebSocket API
- 37 FX Venues
- 14 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
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 645 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 916 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛