How to use Secondary and custom fields in API calls?

Hello Team,
Can you please inform us what are the secondary fields and custom fields we can pass to 'cases/screeningRequest' and 'reference/profile/' API? What is format(syntax) we can pass these fields?
Best Answer
-
Hi @pmahamunee,
You can get the details of the custom fields and the secondary fields from the API call - 'SEQ-pre-group-case-template: Get the case template for a group'.
Please note, that the custom fields needs to be created using the World-Check One UI. Once you have created the custom fields via the UI, the same will reflect in the above mentioned API call and used.
For a custom field you will have to define your own typeID and its curresponding value. For secondary fields values, World-Check One provides in your case template (Above mentioned API call).
If you wish to not include custom fields in your request payload you can just delete them from your request payload and pass the request.
World-Check One provides the functionality of passing custom fields as part of your request payload to track additional details at your end and are solely to be used from your end. The fields that you set form custom fields will not contribute in screening against World-Check One data.
Custom Fields :
If you are using the custom field, the request payload would be in the below format -"customFields": [ { "typeId": "0a3687d0-6334-14a5-98e4-2dd200000f22", "value": "Test_custom_field" }]
If you are not using any custom field, the value for custom field would be in below format -"customFields": []
Secondary Fields :
The secondary field information is passed in the below format :"secondaryFields":[{ "typeId": "SFCT_1", "value": "MALE", }, { "typeId": "SFCT_2", "dateTimeValue": "1962-09-07" }, { "typeId": "SFCT_3", "value": "IND", }]
If you are not using any secondary field value in the secondary field, you may pass it blank, like below -"secondaryFields":[]
Please note: the the value of the secondary fields are below -
SFCT_1 – GENDER
SFCT_2 – DOB
SFCT_3 – COUNTRY LOCATION
SFCT_4 – PLACE OF BIRTH
SFCT_5 – NATIONALITY
SFCT_6 – REG. COUNTRY (ORGANISATION)
SFCT_7 – IMO # (VESSEL)Hope this helps.
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
- 249 ETA
- 554 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
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 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 中文论坛