Unable to request MEDIA_CHECK via API

Paul.Weaver
Paul.Weaver Newcomer
in World-Check One

We have a trial account for the World Check One API and we can't post a request to the /screeningRequest endpoint (perform synchronous screening for a new case) if we include MEDIA_CHECK in the provider types. We're making the call from a simple C# class. We were previously able to do this, and the code at our end hasn't changed, so I think it must be something to do with the account settings. We can screen a new case with Media Check from the web site, and we can screen a case via the API if we don't include MEDIA_CHECK in the ProviderTypes array in the request. But if we ask for WATCHLIST and MEDIA_CHECK, we get 403 Forbidden. I've already raised a support ticket and they have directed me here. We have two Groups in our account, and both have Media Check listed under Product Entitlements. Can you help?

Tagged:

Best Answer

  • judith.pillado.lseg
    judith.pillado.lseg LSEG
    Answer ✓

    Hi @Paul.Weaver, thank you for providing that! After looking into your account settings a little further, I noticed you do not have Media-Check API access:
    1661300162387.png
    The above setting should also include Media-Check, and since it is not enabled, you are getting the error you mentioned. In order to get this enabled, kindly speak to your integration/solutions consultant. If you have any further questions, please let me know!


    Thanks,

    Judith

Answers

  • judith.pillado.lseg
    judith.pillado.lseg LSEG

    Hi @Paul.Weaver, thank you for reaching out to us! I would be happy to help.

    One of the things we have to keep in mind is that even though you have Media Check enabled in your account, you do NOT have Media Check OGS at initial screen:
    1661187262935.png

    Having said that, would you please send me the request body you are trying to send so that I can investigate further (assuming that you are not trying to do Media Check OGS as I have mentioned above)?

    Thanks,

    Judith

  • Paul.Weaver
    Paul.Weaver Newcomer

    Thank you for your help with this. As far as I know I'm not requesting OGS, unless it's being requested by default and I haven't realised. I have since examined the error object that comes back with a rejected request:

    error: MEDIA_CHECK_UNAVAILABLE
    cause: This operation has failed. You do not have Media-Check entitlement.

    I've posted two request bodies below. The first is accepted, the second gets 403 Forbidden.

    {
    "entityType": "INDIVIDUAL",
    "groupId": "5jb6qi8bd7i21ghxrxn4m2rxi",
    "caseId": "PRH0823A",
    "name": "John William Smith",
    "providerTypes": [
    "WATCHLIST"
    ],
    "secondaryFields": [
    {
    "value": "MALE",
    "typeId": "SFCT_1"
    },
    {
    "dateTimeValue": "1956-09-23",
    "typeId": "SFCT_2"
    },
    {
    "value": "GBR",
    "typeId": "SFCT_3"
    },
    {
    "value": "GBR",
    "typeId": "SFCT_4"
    },
    {
    "value": "GBR",
    "typeId": "SFCT_5"
    }
    ]
    }

    {
    "entityType": "INDIVIDUAL",
    "groupId": "5jb6qi8bd7i21ghxrxn4m2rxi",
    "caseId": "PRH0823B",
    "name": "John William Smith",
    "providerTypes": [
    "WATCHLIST",
    "MEDIA_CHECK"
    ],
    "secondaryFields": [
    {
    "value": "MALE",
    "typeId": "SFCT_1"
    },
    {
    "dateTimeValue": "1956-09-23",
    "typeId": "SFCT_2"
    },
    {
    "value": "GBR",
    "typeId": "SFCT_3"
    },
    {
    "value": "GBR",
    "typeId": "SFCT_4"
    },
    {
    "value": "GBR",
    "typeId": "SFCT_5"
    }
    ]
    }

  • Paul.Weaver
    Paul.Weaver Newcomer
    https://community.developers.refinitiv.com/discussion/comment/97024#Comment_97024
    Thanks again for your help. We were able to get the appropriate access enabled and everything is working now.

Categories