404 Returned from MediaCheck API call

After creating a case, for an entity with known negative news (BMW US Capital), I record the SystemCaseID (5nzbfkd6uwje1f2gspmb1o3uk) , and then make a POST request to:
https://rms-world-check-one-api-pilot.thomsonreuters.com/v1/cases/5nzbfkd6uwje1f2gspmb1o3uk/mediacheck/results
With the body:
{
"pagination": {
"itemsPerPage": 25,
"sort": "NEW_TO_OLD"
}
}
This returns with a 404 error, with a error body of "[]"
What am I doing wrong?
Best Answer
Answers
-
@GDC,
Thank you for your query.
Can you please confirm if you have saved / screened the case against MEDIA_CHECK providerTypes or just WATCHLIST providerType?
For Media Check results, the case should be saved and screened using the below providerTypes -
"providerTypes": [
"WATCHLIST", "MEDIA_CHECK
],Hope this clarifies your concern.
0 -
When I try to save the case using the "MEDIA_CHECK" providerType, I get a different error:
So; if I save the case:
{
"secondaryFields": [
{
"typeId": "SFCT_6",
"value": "USA"
}
],
"entityType": "ORGANISATION",
"customFields": [],
"groupId": "5nzbfkd2er2g1f0dnw7zebv48",
"providerTypes": [
"WATCHLIST",
"MEDIA_CHECK"
],
"name": "BMW US Capital"
}I get this error back:
[
{
"error": "INVALID_PROVIDER_TYPE",
"cause": "Provider types are invalid and must include at least WATCHLIST."
},
{
"error": "INVALID_ENTITY_TYPE",
"cause": "Entity type is mandatory and must be one of: INDIVIDUAL, ORGANISATION, VESSEL, UNSPECIFIED and must be compatible with each provider type used in screening a case."
}
]I don't get this error if I just use "WATCHLIST" only.
This error looks quite similar to this other post:
Where the issue was product entitlements, how are these managed?
0 -
@PrabhjyotPrabhjyot - please see my comment below (It's listed as an "Answer" but should have been a reply)
0 -
@GDC - Your account does not have Media Check enabled, so you are unable to screening using it.
Next response in the following link - https://community.developers.refinitiv.com/questions/67418/product-entitlement-how-are-they-managed.html
0 -
I have now added "Media Check" to the product entitlements (see screenshot), and I am screening the case with both
"WATCHLIST" and "MEDIA_CHECK"
However I am still getting a 404 Error when I call
With
{
"pagination": {
"itemsPerPage": 25,
"sort": "NEW_TO_OLD"
}
}Why still a 404 error ?
0 -
Hi,
I tried calling https://rms-world-check-one-api- pilot.thomsonreuters.com/cases/5nzbfkd9gzqv1f2rxl07ze6dw but it times out. I've even left it for 10 minutes, but the API never responds. - So sorry, I can't get that detail for you.
The media-check does work through the web-interface (worldcheck.refinitiv.com) though.
It seems to happen with any company I try, I've used "Apple", "Facebook", "BMW US Capital" etc.
Any tips or solutions are very welcome!
Fiach
0 -
Hi again...
Sorry, ignore that last message, I forgot the "v1" in the URL.
Here is the Json response;
{
"caseId": "5nzbfqact64h1f2rxvb5sjq8v",
"name": "BMW US Capital",
"providerTypes": [
"WATCHLIST",
"MEDIA_CHECK"
],
"customFields": [],
"secondaryFields": [
{
"typeId": "SFCT_6",
"value": "USA",
"dateTimeValue": null
}
],
"groupId": "5nzbfkd2er2g1f0dnw7zebv48",
"entityType": "ORGANISATION",
"caseSystemId": "5nzbfqact64h1f2rxvb5sjq8w",
"caseScreeningState": "INITIAL",
"lifecycleState": "UNARCHIVED",
"creator": {
"id": "5nzbfkd2er2g1f0dnwnrn8azi",
"firstName": "Fiach ",
"lastName": "Reid",
"fullName": "Fiach Reid",
"email": "rd@globaldataconsortium.com",
"status": "ACTIVE",
"registrationKey": "86225f66-8f83-45c5-ae94-8faef8be2bac:86225f66-8f83-45c5-ae94-8faef8be2bac",
"userId": "5nzbfkd2er2g1f0dnwnrn8azi"
},
"modifier": {
"id": "5nzbfkd2er2g1f0dnwnrn8azi",
"firstName": "Fiach ",
"lastName": "Reid",
"fullName": "Fiach Reid",
"email": "rd@globaldataconsortium.com",
"status": "ACTIVE",
"registrationKey": "86225f66-8f83-45c5-ae94-8faef8be2bac:86225f66-8f83-45c5-ae94-8faef8be2bac",
"userId": "5nzbfkd2er2g1f0dnwnrn8azi"
},
"assignee": null,
"creationDate": "2020-10-16T13:13:05.645Z",
"modificationDate": null,
"outstandingActions": true
}Hope this Helps!
0 -
*Just bumping this question* - any idea why I'm getting a 404? Perhaps I'm missing a step?
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 698 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 2.9K Elektron
- 1.5K EMA
- 257 ETA
- 565 WebSocket API
- 40 FX Venues
- 16 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.1K Refinitiv Data Platform
- 800 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
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 232 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 101 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛