Using the Postman collection and trying to retrieve media check results

{{protocol}}{{gateway-host}}{{gateway-url}}cases/{{case-system-id}}/mediacheck/results

I am receiving the error response:

[
{
"error": "INVALID_PROVIDER_TYPE",
"cause": "This operation has failed. You specified case ID without MEDIA_CHECK provider."
}
]

But looking at https://developers.lseg.com/content/dam/devportal/en_us/product-docs/wc1-api/documentation/v2/schema-reference/wc1-api-schema-reference-documentation.html#tag/media-check/operation/getMediaCheckDetails

I cannot see a way to specify the MEDIA_CHECK provider

1. Updating Existing Screenings with Adverse Media
   We have already created multiple individual screenings without selecting the Adverse Media option. We would now like to include Adverse Media screening for a list of entities that have already been screened.
   • Is there a bulk update API or bulk action available to re-run the screening for all existing records with Adverse Media enabled?
   • If the screenings are re-run, will previously confirmed hits or false positives need to be re-reviewed and re-confirmed?
2. Transposition Feature Behavior
   We tested the Enable Transposition feature and observed differences in the Adverse Media results. Specifically, we created two individual screenings for “Keir Starmer”:
   • One screening with the name entered as “Starmer Keir” and Enable Transposition selected
   • Another screening with the name entered as “Keir Starmer” without transposition

The World-Check results were the same in both cases; however, the Adverse Media results were different. In particular, no Adverse Media results were returned for “Starmer Keir.”

Could you please explain why this occurs? Is this expected behavior for the transposition feature?

How do I get access to create a WC1 service account? Currently, I can only add a normal user.

I am reaching out for help with understanding the World Check functionality as a not-experienced user of this application.

My client uses World-Check Customer Risk Screener.
Recently I was notified that automatic rescreening of individual screening cases does not work.

Here is what I mean:
Once the review of the client's client is started, there is a flow (salesforce automation) responsible for triggering an invocable action "Automate Screening" (apex-tr_wc1__tr_automateScreening) with an Apex Class behind.
As I understand, this action should send a request to World Check One to review the individual based on which we should receive a response on the Screening Case record in Salesforce.

This unfortunately does not happen. After some tests, it was figured out that once "Ongoing Screening Enabled" is set to TRUE on the Screening Case, the action is successful and the update is received on the screening case record in Salesforce.

What is interesting, for Entity Type Organisation Screening Cases, Ongoing Screening is enabled in the client's org.

It would seem natural to set this checkbox to TRUE everywhere, but before doing that I would like to understand the potential impact of enabling this feature. While going through the documentation (Document Version 2.1 Date of issue: 19 February 2020) I couldn't find any extensive explanation or answer to my questions.

May I ask here for a helping hand?

Many thanks in advance!

But our users would prefer to rely on matching solely on anglicized names. So we wonder if it is possible to toggle translation/transliteration off either as an organization level setting or on a per-case basis.

Alternatively, is there an option to anglicize the native AKA matches when they are not in the Latin alphabet?

We are assisting a customer with World-Check One API onboarding. In the Excel Sheet for Technical Validation, there is a reference to “User Activity Monitoring (Enables the customer to create their own home-grown customized case manager)”

Could you confirm:

1. The exact meaning of this feature?
2. Which API endpoints support this functionality?

1. Is it possible to retrieve detailed information in bulk for multiple search results via the World-Check One API?
They have reviewed the available documentation but have not identified any method that supports bulk access. Currently, they are sending individual GET references/records/{{worldcheck-record-id-encoded}} requests for each result to obtain Records. However, this approach often leads to 429 Too Many Requests errors due to the volume of requests. If there is a method—such as a specific API endpoint—that allows bulk retrieval, your guidance would be greatly appreciated.

2. If bulk retrieval is not supported via the World-Check One API, would the only alternative be to use WCOD or WCDF to obtain detailed information?
They are considering optimization options and would like to understand whether WCOD or WCDF provides a viable solution for bulk access to Watchlist Record details.

Any insights or recommendations you can provide on these two points would be very helpful.

Thanks,
satom

I am doing callout from post but json i got with custom filed empty list . Please help to Fix and get the custom Field Id

We have successfully implemented and tested WorldCheckOne integration in our development stage. HMAC-Authorization worked perfectly fine. We are now testing on the acceptance stage at our customer, where all requests are routed through an Enterprise Service Gateway. This means that our request goes to "gateway.internal" instead of to "api.risk.lseg.com". The ESG later forwards the request to "api.risk.lseg.com".

Since the (request-target) and "host" are part of the HMAC, we implemented a workaround, where we create the HMAC based on the future values that the ESG will set when forwarding and rewriting the request. At least according to our Unittests this works. Unfortunately, the customer's ESG does (in our eyes) not behave properly and does not update the Host header. I.e. the Host header in the outbound request still contains "gateway.internal" instead of "api.risk.lseg.com". (We are in discussion with our customer whether they can fix/configure the ESG to properly update the Host header).

My question now is: Does the WorldCheckOne-API require that the Host header be "api.risk.lseg.com", or does it blindly use the Host header value from the request to compute the HMAC for verification? If so, we could simply keep using "gateway.internal" and also use that for the HMAC on our side.

This would mean that the text-to-sign would look like this:

(request-target): post /screening/V3/cases
host: gateway.internal
date: Tue, 07 Jun 2016 20:51:35 GMT
content-type: application/json
content-length: 88
{
"caseId": "my customer ID",
"name": "John Doe",
"providerTypes": ["WATCHLIST"]
}

instead of the "correct":

(request-target): post /screening/V3/cases
host: api.risk.lseg.com
date: Tue, 07 Jun 2016 20:51:35 GMT
content-type: application/json
content-length: 88
{
"caseId": "my customer ID",
"name": "John Doe",
"providerTypes": ["WATCHLIST"]
}

We are migrating from WC1 V1 to V3, and so far we have been iterating through OGS updates by specifying updatedDate in the query field and sorting by updateDate, for example:

{  "pagination": {   
    "currentPage": 1,    
    "itemsPerPage": 20  
},  "sort": [   
 {      "columnName": "updateDate",      "order": "ASCENDING"    }  
],  "query": "updateDate >= '2025-09-23T07:54:47.2449730Z'"
}

Could you please advise on the recommended way to achieve the same in V3?
It looks like we need to use RANGE to filter by updateDate, but it seems that sorting by updateDate is not supported.

{    "filter": "updateDate=RANGE=(2020-12-06T23:59:59Z,2025-08-20T18:00:00Z); providerType==WATCHLIST",    "mode": "SUMMARY",    "sort": [        {            "columnName": "updateDate",            "order": "ASCENDING"        }    ],    "pagination": {        "itemsPerPage": 100,        "pageReference": null    }}
```

Then I got the 404 notfound error response.

```
{    "id": "04e174fd-9722-416c-b313-6225dbb5bd1c",    "status": "404",    "errors": [        {            "code": "NO_OGS_CASE_UPDATES_FOUND_WITHIN_DATE_RANGE",            "message": "No ogs case updates found within date range."        }    ]}

```

Is this meannig I have no updated results by OGS screening? Or I made a mistake of calling the api?
I checked the WC1 GUI. In case manager, the "Last Screened Date" was updated by the time of OGS screening.
One of them was set "Last Modified Date-OGS:05-Apr-2024 00:16". It means there was results by OGS screening, but It was too old to respond, rigth?
If that is right, how can I get results by OGS screening? (How to create data easy to be checked by OGS screening.)

Thanks,
satom.

1.Alerts for shareholder changes
2.Alerts for changes in ownership ratios
3.Alerts for company name changes

My understanding is that we can not based on below documents

https://developers.lseg.com/content/dam/devportal/en_us/product-docs/wc1-api/documentation/v3/schema-reference/wc1-api-schema-reference-documentation.html#tag/ubo-check

However, if we develop or custermize by using above endpoints and store data, we can catch these information(shareholder changes, changes in ownership ratios, company name changes).

We are glad if you give me some advice about this.

Is there a recommended way to trigger or check notifications more immediately(OGS_UPDATE) from the world check one server ?

If we register a large number of cases, we might be able to receive it short terms, but we are considering whether it is appropriate to make changes using the "Resolution" field, for example, to prompt a faster response.

As far as I understand, only the following notification types are available:

• OGS_UPDATE: which depends on actual data updates and may take time.
• CASE_RESOLUTION: which can be triggered immediately if the case is resolved.

Could you please confirm if this understanding is correct, and advise on best test ways for receiving timely notifications as for OGS_UPDATE?

Many thanks in advance!

Just a question. I got the Notifications call working with no issues. But I have a question about retrieval of subscriptions if you don't have the subscription id.

So, an error occurred, and the subscription id is not logged (after the creation). All the Notification API calls require subscription id to work.

Now I can't recreate a subscription with the same recipient(s) because it tells me the subscription with the recipient already exist. But I don't have the subscription id (the value was accidently not logged). So now I'm stuck.

How do I find all my subscription ids?

Thanks.

There are results in each set that does not appear in the other when compared based on the reference IDs.

I was wondering if there is a full list of categories (with description will be better)?

OFAC published the latest SDN list last Friday and we expected some of our cases to get updated with new matches. They eventually did, but with a longer delay then expected.

What I noticed is that there was a significant (as much as 35-48 hours in some cases) delay between the record being updated (based on the modificationDate) and the new result appearing on the case (creationDate of the result).

Is that delay expected? In one of the questions I saw that OGS checks run at 18:00. I'm not sure if that is still the case. Are they based on the latest entity information? If the entity was updated before the OGS start, can we not expect it to be considered in the OGS check?

To summarize it, using specific data. The record (e_tr_wco_8608880) was updated on the 20th, at 00:00:00 (?) UTC, but the corresponding result (5jb743qlqqam1js87w8wxbsmd) only showed up on the case at 2025-06-22T03:59:50.717Z.

I’m currently working on a research project aimed at developing a firm-level geopolitical risk index using textual analysis of earnings call transcripts. For this purpose, I’m looking to access historical transcripts across a large sample of firms — ideally around 10,000 companies — and spanning multiple years.

From what I understand, LSEG provides extensive coverage of transcripts (~40,000 per year, from 10,000 companies globally) via the Transcripts & Briefs product (see below screenshot). The delivery mechanism includes API, Desktop, and Excel, and formats such as JSON, XML, and Text — which is ideal for my use case.

I currently have access to LSEG through my university (University of Edinburgh) but I’m unsure how to actually retrieve this data — especially in bulk.

I would really appreciate any guidance on how to access the data whether it can be accessed through API key, or others method.

Thank you in advance for your help!

Best regards,
Zahra
MSc Business Analytics, University of Edinburgh

We are performing API calls to perform screening as part of an application workflow. I'm wondering is there a way to perform them on behalf of, or acting as a user within the group?

Currently all of our audit logs and thus case summaries are showing as the Admin User the API secret was issued for. We'd like to make our audit via the API consistent with UI queries which at present it won't be.

Any information would be appreicated.

What are the possible values returned in the fieldResult field by the Refinitiv API, and what does each value represent?

For example: MATCHED, NOT_MATCHED, etc.

Thank you in advance.

I'm encountering a persistent 401 Unauthorized error when calling https://api.risk.lseg.com/screening/v3/cases?screen=SYNC from my Java application.

Notably, the API works fine when tested directly within the WC1 environment. However, the same request (or equivalent cURL generated) consistently returns a 401 when made as a new request from my development setup.

I've already verified the API credentials, groupId, and system time synchronization.

Attached are the cURL command for your review.

Please advise on a resolution.

The documentation states the following:

DELTA_SYNC: Update; and delta screen the case synchronously against new and updated data from the last screened date. Example: If case was last screened on 01-Feb-2025, using DELTA_SYNC will screen the case against new and updated data since 01-Feb-2025 until the current day. You may also use this option to just perform delta screening on the case without giving any request payload if you do not want to update the case.

we've tried sending over an empty request body but we get a 401 Unauthorized. However, sending the following in the request body with the same entity information works:

{
"caseId": "",
"groupId": "{{group-id}}",
"entityType": "INDIVIDUAL",
"providerTypes": [
"WATCHLIST"
],
"caseScreeningState": {
"WATCHLIST": "INITIAL"
},
"name": "Entity Information",
"nameTransposition": false,
"secondaryFields": [
{
"typeId": "SFCT_5",
"value": "XXX"
},
{
"typeId": "SFCT_3",
"value": "XXX"
}
]
}

is there a reason why we can't leave the request body empty?

Can we assume in our application that the particular entity will stay "removed"? Will it ever reappear again?