Hi everyone!
Here are this month’s highlights for upcoming changes, allowing you to adjust your integration in advance. Please take a minute to review and plan any updates.
Changes to come into effect July 15
Russian securities (NSD / EO 14071) will be reclassified from sanction to invest.ban
Effective date: 2026-07-15
From July 15th, securities issued by the Russian National Settlement Depository (NSD) will be tagged invest.ban (Investment ban) to more accurately reflect their status: Executive Order 14071 is not a designation of any particular securities, but is rather a prohibition of certain conduct by US persons, including a jurisdiction-wide investment ban. So far, these securities have been tagged with the sanction topic.
These entities will continue to be included in the securities.csv download, under eo_14071. See our securities docs for more.
A technical effect of this more accurate classification of NSD securities is that the issuers of other securities tagged with the sanction topic will be tagged as sanction.linked.
Properties affected: Thing:topics
Datasets affected: approximately 18k Securities in Russian National Settlement Depository (NSD, ISIN Assignment)
Upcoming changes
New feature: New ofac matching algorithm
Effective date: 2026-06-30
We’ve released a new name matcher, ofac, which emulates the public OFAC Sanctions List Search tool at sanctionssearch.ofac.treas.gov with ±5% parity. Read more about how this came about in our blog post.
(As a consequence, we’ll be retiring the name-based and name-qualified algorithms in January 2027.)
Important change: HTTP Redirects from data.opensanctions.org/datasets/ (changelog)
Effective date: 2026-08-17
Please check that your configuration supports HTTP 307 redirects for HTTP requests to data.opensanctions.org. Starting in August, the site may redirect users attempting to fetch a specific data export to an updated location.
The canonical location will now be at /datasets/, where previously a mix of datasets/latest/ and /datasets/YYYYMMDD/ were used.
The goal of this change is provide immutable addresses for each data export, helping to more clearly identify versions of the dataset.
Removal of id statements from the /statements API (changelog)
Effective date: 2026-07-15
The statement-level API available at the /statements endpoint currently includes id metadata statements that are only used internally by OpenSanctions for change detection. These statements have caused some confusion, so we have recently removed them from the statements.csv data export, and will now do the same for the API.
New property: abbreviation (changelog)
Effective date (end of backwards compatibility): 2026-09
A new abbreviation property now stores shortened entity names (e.g. ANC, IKEA) separately from full names, allowing more precise matching on acronyms. For backward compatibility, values are currently copied to weakAlias. This backstop will be removed in September 2026. Data users are advised to integrate the new property before then. Support was added in yente 5.1.0.
Breaking change (on-premise only): Upgrade to Elasticsearch 9 (changelog)
Effective date (end of life for 8): 2027-01-15
Elasticsearch 9 was released in April 2025, and the end of maintenance for version 8 is January 15, 2027. On-premise customers who are using Elasticsearch need to upgrade their Elastic server to version 9 before January 15, 2027. Current versions of yente are already compatible with both version 8 and 9 of the Elastic server, but yente 5.4.0 released in May 2026 is the last version compatible with Elastic server 8. You can find information on how to upgrade a standard single-node setup of Elastic in our documentation. For more advanced setups, please refer to the official Elastic documentation.
We recommend that on-premise customers perform this upgrade together with one of their upcoming upgrades of yente.
Recent changes
New yente 5.5.0 (changelog)
Released: 2026-06-23
This release is mostly a maintenance and hardening release: yente now requires an Elasticsearch 9.x server, verifies the integrity of downloaded entity data via checksums, exposes index freshness as an OpenTelemetry gauge, and ships container images with signatures and bill-of-materials attestations for downstream supply-chain scanners.
More details in the release notes, and here’s the announcement on the discussion forum in case you have any questions.
Turning iso9362_bic into an enrichment dataset: ext_iso9362_bic (changelog)
Effective date: 2026-06-15
On June 15th, 2026, we removed the full BIC Reference Data (iso9362_bic) from the default collection and replaced it with Business Identifier Code (BIC) Reference Data (ext_iso9362_bic), an enrichment dataset containing only the risk-related entities from this source.
Dataset removals and deprecations
Lithuania PEPs from the register of private interests (lt_pep_declarations) to be removed August 17th (changelog).
New datasets
Canadian Consolidated Autonomous Sanctions List on the Russian invasion of Ukraine (ca_sema_sanctions_news)- Germany Banned organizations involved in foreign-related extremism (
de_bfv_extremism) - Philippines GPPB Consolidated Blacklisting Report (
ph_gppb_debarred) - Tunisia National Counter-Terrorism List (
tn_cnlct) - US FINRA Barred Individuals (
us_finra_barred) - US National Provider Identifier Registry (
ext_us_cms_npi)
And many more!
Quick reference
- Data dictionary — Full property and schema documentation
- Crawler planning — See what’s in progress and vote on priorities. Submit new data source requests via the request form or email support@opensanctions.org.
- Changelog — A record of significant data and API changes; see also yente release notes
- Community forum — Questions, discussion, and announcements
- Status page — Live service status and incident history