Provider type not accepted
When sending a request for creating multiple cases using /saveAndScreen i get:
400 Bad Request: "[{"error":"INVALID_PROVIDER_TYPE","cause":"Provider types are invalid and must include at least WATCHLIST."}]"
What is wrong with the request?
Request body:
{
"groupId":"5jb6u0gde8tu1fkacjta3o9p7",
"providerTypes":[
"WATCHLIST"
],
"cases":[
{
"caseId":null,
"entityType":"VESSEL",
"name":"ABAN II",
"customFields":[
{
"typeId":"5jb7m2seyqae1hmr59e00gpkx",
"value":"8750015",
"fieldValueType":"TEXT",
"regExp":null,
"fieldRequired":false,
"label":"vesselId"
}
],
"secondaryFields":[
]
}
],
"nameTransposition":false,
"caseScreeningState":{
"watchlist":"INITIAL"
}
}
Best Answer
-
Hello @eirik.yksnoy, thank you for reaching out to us! Kindly look at the request body schema within the API endpoint Save and screen multiple cases (also seen in our WC1 API documentation).
{
"groupId": "{{group-id}}",
"providerTypes": [
"WATCHLIST"
],
"nameTransposition": false,
"caseScreeningState": {
"WATCHLIST": "INITIAL"
},
"cases": [
{
"entityType": "ORGANISATION",
"name": "Stark Enterprise"
},
{
"entityType": "INDIVIDUAL",
"name": "Tony Stark",
"secondaryFields": [
{
"typeId": "SFCT_1",
"value": "MALE"
},
{
"typeId": "SFCT_2",
"dateTimeValue": "1980-01-18"
},
{
"typeId": "SFCT_3",
"value": "USA"
},
{
"typeId": "SFCT_4",
"value": "AUS"
},
{
"typeId": "SFCT_5",
"value": "ABW"
}
],
"customFields": [
{
"typeId": "{{custom-field-1}}",
"value": "custom field 1 sample value"
},
{
"typeId": "{{custom-field-2}}",
"value": "custom field 2 sample value"
},
{
"typeId": "{{custom-field-3}}",
"value": "mandatory custom field sample value"
}
]
},
{
"entityType": "INDIVIDUAL",
"name": "Dr. Stephen Strange"
},
{
"entityType": "VESSEL",
"name": "The Black Pearl",
"secondaryFields": [
{
"typeId": "SFCT_7",
"value": "9362059"
}
]
}
]
}When you compare your request body with the one above, the attribute within "caseScreeningState" called "WATCHLIST" is completely capitalized, while your attribute within "caseScreeningState" is not capitalized. This causes you to get a 400 error.
It is very important to always make sure you follow the request body schema because it is your guide to getting a successful response.
Kindly fix your request body and let me know if you are able to get a successful response. Thank you.
Blessings,
Judith
0
Answers
-
The cause was the lowercase watchlist field. We are using Java/Spring Boot and the class CaseScreeningState has a field called watchlist. This field was always lowercase in the json payload. It was fixed by adding @JsonProperty("WATCHLIST") to the field.
Thank you!
0 -
Hello @eirik.yksnoy - thank you for the update and I am glad everything is working out smoothly for you now! Let me know if you need anything else.
Blessings,
Judith
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛