INVALID_MESSAGE_FIELD_FORMAT lowercase providerTypes

For my ZFS POST /screening/v3/cases request, I get the following response:
{"id":"424af957-2110-48de-81d2-84f1e679a15f","status":"400","errors":[{"code":"INVALID_MESSAGE_FIELD_FORMAT","message":"Message field '.providerTypes[0]' has an invalid value.","error":null}]}
The request includes:
"providerTypes":["watchlist"]
I have figured out, that it is supposed to be "providerTypes":["WATCHLIST"]
(all uppercase). This is however not clear from the API documentation. The relevant excerpt from the openapi spec:
ProviderType: type: string description: Provider type enumeration. x-wc1-not-value: true enum: - watchlist - passportCheck - mediaCheck - clientWatchlist - uboCheck x-enum-varnames: - WATCHLIST - PASSPORT_CHECK - MEDIA_CHECK - CLIENT_WATCHLIST - UBO_CHECK
openapi-generator (for Java) generates the following enum:
public enum ProviderTypeDto { WATCHLIST("watchlist"), PASSPORT_CHECK("passportCheck"), MEDIA_CHECK("mediaCheck"), CLIENT_WATCHLIST("clientWatchlist"), UBO_CHECK("uboCheck"); }
To me it seems the API-specification is incorrect here, as the listed values should all be uppercase. Unless the providerType differs between normal screening and ZFS screening, which could be the case based on the API description:
Array of strings (ProviderType) non-empty unique Items Enum: "watchlist" "passportCheck" "mediaCheck" "clientWatchlist" "uboCheck"
Provider types required to Screen this Case.For 'Zero Footprint Screening (ZFS)', only 'WATCHLIST' is supported.
If so, the OpenAPI-specification should list WATCHLIST
as one of the valid enum
values.
Best Answer
-
Hi @marc_etter,
Thank you for reaching out. Please be aware that V3 is still in early access, so you may encounter some bugs, incomplete features, and documentation issues. Your feedback is invaluable in helping us resolve these efficiently. We will also communicate your concerns to our product team to address these issues.
Thanks,
Ram.
1
Answers
-
I see, thank you. What is the rough ETA for V3 to be fully released?
0 -
We tentatively anticipate the official launch by the end of Q1.
1 -
Thanks! Just to make sure - you are talking about Q1 2025, right?
0 -
Yes, we are referring to Q1 2025.
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
- 685 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
- 252 ETA
- 556 WebSocket API
- 38 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
- 651 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
- 917 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 中文论坛