2025

Release Notes for 2025

1.1.2 - 29 August 2025

Fixed an issue where records that are formerly associated with Iran Economic Interest (IEI) keywords are not being returned by the API.

Fixed an incorrect value for meta.requestId in the References API response.
Fixed incorrect values of the lastPublishedDate for a few records that were missed during the timestamp remapping.

For PILOT / Early-Access Participants

Please do a one-time full refresh of your WCOD records and references after 19 August 2025.

The client-facing data has been fully reloaded from the legacy backend to apply the latest transformations and data fixes.
The initialPublishedDate has been made to match the CREATED date of the same record UID in World-Check Data File (WCDF). New records after this point will have different values for this field between the two systems due to the timing and publication frequency differences.
As a one-off activity, the lastPublishedDate of each first published record in World-Check On Demand has been made to closely match the latest UPDATED date of the same record UID in WCDF. Similar to the previous item, record updates after this point will have different values for this field between the two systems. Records are expected to be published earlier in World-Check On Demand.

On rare occasions, records published for the first time can have an Update Category value that is not wcUpdateCat:C0. This is expected behavior and is due to certain internal processes. Regardless of the update category, records published for the first time will always have their lastPublishedDate equal to the initialPublishedDate. Only the lastPublishedDate gets updated on subsequent updates for the same record UID.
The burst rate limit per account (token bucket) for an endpoint has been raised from 5 to 25 concurrent requests.
The maximum rate limit per account for an endpoint has been raised from 50 to 250 requests per second.

Fixed the intermittent http/502 (Bad Gateway) errors during high-traffic scenarios.
Reduced the time it takes to retrieve large records, significantly lowering the probability of getting http/504 (Gateway Timeout) errors.
Fixed the issue where the initialPublishedDate of record updates (i.e., not the first version of the record) have the same value as the recent lastPublishedDate.

The World-Check On Demand API v1.0 endpoint is available at https://api.risk.lseg.com/data/world-check/v1/.
The following paths are still active but direct to the same API v1.0 backend:
- https://api.refinitiv.com/risk-intel/beta4/ (deprecated - please change to /v1)
- https://api.refinitiv.com/risk-intel/v1/
Existing Pilot / Early-Access participants can continue using the basepath https://api.refinitiv.com/risk-intel/ if there are immediate constraints in shifting over to the new lseg.com URL. However, the path should be changed to /v1. The token request endpoint remains as https://login.ciam.refinitiv.com.
Performance enhancement for the Record Count feature, reducing processing time to just a few seconds and avoiding a Gateway Timeout. However, this improvement is limited to only the following:
- Record count without any filters (i.e., all records)
- Record count with the lastPublishedDate filter, without any other filter in the query. This is intended to help validate count of retrieved records during delta runs.
The initialPublishedDate and lastPublishedDate of WCOD records have been updated to match or have a close value with the equivalent record in World-Check Data File (WCDF):

WCOD Field	WCDF Field	Notes
`initialPublishedDate`	`ENTERED`	Exact
`lastPublishedDate`	`UPDATED`	Exact or close