Is it possible to perform Pasport-check via WC1 API?

when calling API to check the passport check I get an error msg
{"The remote server returned an error: (401) Unauthorized."}
{
"secondaryFields": [
{
"typeId": "SFCT_1",
"value": "MALE"
},
{
"typeId": "SFCT_2",
"dateTimeValue": "1985-07-01"
},
{
"typeId": "SFCT_3",
"value": "IRQ"
},
{
"typeId": "SFCT_8",
"value": "mustafa"
},
{
"typeId": "SFCT_9",
"value": "alridha"
},
{
"typeId": "SFCT_11",
"value": "IRQ"
},
{
"typeId": "SFCT_12",
"value": "IRQ"
},
{
"typeId": "SFCT_14",
"value": "PASSPORT"
},
{
"typeId": "SFCT_15",
"value": "A13559370"
},
{
"typeId": "SFCT_16",
"dateTimeValue": "2026-05-29"
}
],
"entityType": "INDIVIDUAL",
"customFields": [],
"groupId": "5jb72iaaccb41fmgj14jynwu9",
"providerTypes": [
"WATCHLIST",
"PASSPORT_CHECK"
],
"name": "mustafa",
"nameTransposition": false,
"caseid": ""
}
Best Answer
-
Hi @fadi.alsayyed
Thanks for reaching out to us!
We have verified your request payload and found out that your request is missing the required secondaryFields (below), once we have added these required secondaryFields we are getting the successful response.
"typeId": "SFCT_10"
"typeId": "SFCT_13"
*Please find the sample request payload below*{
"groupId": "{{group-id}}",
"entityType": "INDIVIDUAL",
"caseId": "",
"providerTypes": [
"WATCHLIST",
"PASSPORT_CHECK"
],
"name": "mustafa",
"nameTransposition": false,
"secondaryFields": [
{
"typeId": "SFCT_1",
"value": "MALE"
},
{
"typeId": "SFCT_2",
"dateTimeValue": "1985-07-01"
},
{
"typeId": "SFCT_3",
"value": "IRQ"
},
{
"typeId": "SFCT_8",
"value": "mustafa"
},
{
"typeId": "SFCT_9",
"value": "alridha"
},
{
"typeId": "SFCT_10",
"value": "MALE"
},
{
"typeId": "SFCT_11",
"value": "IRQ"
},
{
"typeId": "SFCT_12",
"value": "IRQ"
},
{
"typeId": "SFCT_13",
"dateTimeValue": "1985-07-01"
},
{
"typeId": "SFCT_14",
"value": "PASSPORT"
},
{
"typeId": "SFCT_15",
"value": "A13559370"
},
{
"typeId": "SFCT_16",
"dateTimeValue": "2026-05-29"
}
],
"customFields": []
}
Kindly note that that the result will be available only in UI. Where would you check the passport check details on the UI? Please see the screenshot:
0
Answers
-
Are all secondary parameters of PASSPORT_CHECK mandatory?
0 -
@urmimala.ghosh ,Hi
The secondary fields SFCT_8 to SFCT_16 is mandatory fields to send in your request body if you are screening against passport check.0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 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
- 248 ETA
- 552 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.8K Refinitiv Data Platform
- 625 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛