Worldcheck API v2.46 - Receive http 415 Unsupported Media Type on Create Case

Hi Support team,
I've encountered Http 415 Unsupported Media Type response when creating new screening case on Pilot Environment.
I am using the Worldcheck One Postman collection v2.46 which is downloaded from API document didn't modify the content and header. Also I found that it seems that the http error code 415 will appear on all POST call but succeed on all GET call.
Could Refinitiv support team please help to support my case? Thanks
curl --location --request POST 'https://api-worldcheck.refinitiv.com/v2/cases'; \
--header 'Date: Mon, 25 Apr 2022 02:29:51 GMT' \
--header 'Content-Type: application/json' \
--header 'Authorization: Signature keyId="9cb09xxxxxxxxxxxxxxxxxxxxxxx",algorithm="hmac-sha256",headers="(request-target) host date content-type content-length",signature="9ML1gmbZZGF8yw+jaP1a7v/+08gZeRZYAG29ZJ/vh7g="' \
--header 'Content-Length: 205' \
--data-raw '{
"secondaryFields": [],
"entityType": "INDIVIDUAL",
"customFields": [],
"groupId": "xxxxxxxxxxxx",
"providerTypes": [
"WATCHLIST"
],
"name": "James Bond"
}'
Best Answer
-
Thank you for your question regarding the updated environment and endpoint collections with version 2.44 and 2.46.
With version 2.46, we have grouped the endpoints within directories which gives the user a much more user-friendly experience. Furthermore, you will find new endpoints such as bulk-actions and audits hence naming version 2.46 as "Case Management and Audit – V2.46.postman_collection"
Please compare the two versions and utilities endpoints as needed for your business- and development needs.
Please find below a brief overview of the two versions in the form of print screens.
If you have any further question, please feel free to contact us.
Regards,
Virgill
0
Answers
-
Upon investigating the error response code you we can advice the following:
To test the World-Check One API endpoints we recommend using the REST client Postman. This is by no means an endorsement of Postman, it is just an example to get you started.
Before posing the desired API call check the following settings within your REST client;
In the Headers of the client settings utilize the Content-Type as Application/Json.
In the Body of the client settings utilize JSON.
Please see below print screen examples. Our API's consumes JSON. Other media types are not supported.
Please check and let us know if you still need our assistance.
Cheers,
Virgill
0 -
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 中文论坛