404 Returned from MediaCheck API call

If Media Check is enabled for your account, you will have to use v2 instead of v1 in the URL, as the Media Check is available on v2.

The endpoint for Media Check results is - /v2/cases/{{case-system-id}}/mediacheck/results

Let us know how it goes.

All comments

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.

https://community.developers.refinitiv.com/questions/49596/client-watchlist-provider-type-is-causing-an-error.html

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?

@PrabhjyotPrabhjyot - please see my comment below (It's listed as an "Answer" but should have been a reply)

@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

https://rms-world-check-one-api-pilot.thomsonreuters.com/v1/cases/5nzbfkd9gzqv1f2o9wmhu6clo/mediacheck/results

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 ?

Can you please share the full case details of the case for which you are getting error 404 for media check results?

API call - SEQ-case-investigate-case-details: Fetch full case details

Endpoint - GET cases/{{case-system-id}}

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

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!

*Just bumping this question* - any idea why I'm getting a 404? Perhaps I'm missing a step?