For a deeper look into our World Check One API, look into:
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"
}'
Hi @productops,
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
Hi @productops,
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
