OpenSanctions

Overview

OpenSanctions offers a centralized and structured dataset of individuals and entities subject to sanctions, as well as those identified as politically exposed persons (PEPs) or listed on various watchlists. The platform collects and normalizes data from over 300 official sources worldwide, including government sanctions lists, law enforcement databases, and financial regulators. This aggregation aims to provide a comprehensive resource for organizations requiring robust anti-money laundering (AML) and know-your-customer (KYC) screening capabilities.

The core offering is a RESTful API that allows programmatic access to this dataset, enabling real-time screening of names and entities against the aggregated watchlists. Developers can integrate this API into their compliance workflows, customer onboarding processes, or internal risk management systems. The API provides structured responses that include details about matched entities, their associated sanctions, and links to source documents, facilitating automated decision-making and manual review processes alike. For scenarios requiring bulk analysis or offline processing, OpenSanctions also provides direct data downloads in formats such as CSV and JSON, allowing for ingestion into bespoke data lakes or compliance platforms.

OpenSanctions is particularly suited for financial institutions, fintech companies, legal firms, and investigative journalists who need to identify potential risks associated with individuals or organizations. Its utility extends to due diligence processes, where verifying the background of business partners or high-net-worth individuals is critical. The service supports compliance with various international regulations by providing access to up-to-date sanctions information. The data collection process emphasizes transparency, with each record linked back to its original source, which can assist in audit trails and regulatory reporting. The commitment to data quality and comprehensive coverage is intended to reduce false positives and ensure accurate risk assessments, a common challenge in sanctions screening as highlighted by industry analysis like those focusing on Dow Jones Risk & Compliance solutions.

Beyond basic screening, OpenSanctions includes features such as entity matching, which helps identify variations of names or aliases, and the ability to search for related entities. This functionality is crucial for uncovering complex ownership structures or networks of individuals attempting to circumvent compliance checks. The platform's focus on structured, machine-readable data aims to streamline the usually labor-intensive process of sanctions screening, making it more efficient and scalable for organizations of all sizes. The availability of a free tier for non-commercial use further supports its adoption by smaller organizations or independent researchers, contributing to broader transparency efforts.

Key features

• Sanctions Data API: Provides programmatic access to a consolidated database of global sanctions lists, enabling real-time screening of individuals and entities. The API offers detailed information on sanctions imposed by various jurisdictions, including the EU, UN, OFAC, and others, with data points such as sanction type, effective dates, and legal basis.
• Watchlist Data: Aggregates data from over 300 sources, including official government watchlists, law enforcement lists, and financial regulatory bodies. This comprehensive dataset extends beyond traditional sanctions to include adverse media, criminal records, and other risk-relevant information, enhancing due diligence processes.
• Politically Exposed Persons (PEP) Data: Identifies individuals holding prominent public functions, their family members, and close associates. This data is crucial for assessing money laundering and corruption risks, a key component of AML/KYC compliance programs globally.
• Entity Matching Service: Utilizes algorithms to identify potential matches between submitted names/entities and records in the OpenSanctions database, accounting for variations in spelling, aliases, and transliterations. This service helps reduce manual review efforts and improve the accuracy of screening results.
• Bulk Data Downloads: Offers the ability to download the entire dataset or specific subsets in machine-readable formats like CSV and JSON. This feature supports offline processing, integration with internal data warehouses, and custom analytics, catering to organizations with large-scale data requirements.
• Transparent Data Sourcing: Each entry in the database includes clear references to its original source, allowing users to verify information and maintain an auditable trail for compliance purposes. This transparency is fundamental for regulatory reporting and demonstrating due diligence.
• Data Freshness: The database is updated regularly, ensuring that users have access to the most current sanctions and watchlist information. This continuous update process is critical for maintaining compliance in a rapidly changing regulatory landscape.

Pricing

OpenSanctions offers a tiered pricing model, including a free option for non-commercial use. Paid plans are structured to accommodate different levels of API usage and data access requirements.

Detailed pricing information and feature breakdowns for each plan are available on the OpenSanctions pricing page.

Common integrations

OpenSanctions' API and data feeds are designed for integration into various compliance, risk management, and data analytics platforms. Common integration points include:

• Customer Relationship Management (CRM) Systems: Integrating sanctions screening into CRM platforms like Salesforce to screen new clients or existing contacts during onboarding and ongoing due diligence.
• Fintech and Banking Platforms: Embedding the API into digital banking apps, payment gateways, and core banking systems for real-time AML/KYC checks during transaction processing or account opening.
• Enterprise Resource Planning (ERP) Systems: Connecting to ERPs such as SAP or Oracle to screen vendors, partners, or employees against watchlists for supply chain risk management or internal compliance.
• Business Intelligence (BI) Tools: Importing bulk data downloads into BI tools like Tableau or Power BI for trend analysis, risk reporting, and forensic investigations.
• Workflow Automation Platforms: Using platforms like Tray.io or Zapier to automate screening requests and trigger alerts based on match results, streamlining compliance workflows.
• Investigative Journalism Tools: Integrating data into research platforms or custom scripts used by journalists to uncover financial crimes or expose illicit networks.
• Identity Verification (IDV) Solutions: Complementing existing IDV services with watchlist data to provide a more comprehensive risk assessment during identity verification processes.

Alternatives

• Refinitiv World-Check: A comprehensive database for financial crime compliance, offering detailed risk intelligence on individuals and entities for KYC, AML, and sanctions screening.
• Dow Jones Risk & Compliance: Provides a suite of data solutions for due diligence, anti-money laundering, and anti-bribery and corruption compliance, including sanctions and PEP data.
• ComplyAdvantage: An AI-driven financial crime insight and AML risk detection platform that uses machine learning to screen for sanctions, PEPs, and adverse media.

Getting started

To get started with the OpenSanctions API, you can make a simple HTTP GET request to their search endpoint. The following Python example demonstrates how to query the API for a specific name.

import requests
import json

API_BASE_URL = "https://api.opensanctions.org/v2/datasets/default/" # Use the default dataset

def search_entity(query_name):
    search_url = f"{API_BASE_URL}search"
    params = {
        "q": query_name,
        "limit": 5 # Limit results to 5
    }
    headers = {
        "Accept": "application/json"
    }

    try:
        response = requests.get(search_url, params=params, headers=headers)
        response.raise_for_status() # Raise an exception for HTTP errors
        data = response.json()

        if data and data.get("results"):
            print(f"Found {len(data['results'])} results for '{query_name}':")
            for result in data["results"]:
                print(f"- Name: {result.get('name')}, Schema: {result.get('schema')}, ID: {result.get('id')}")
                if 'properties' in result and 'birthDate' in result['properties']:
                    print(f"  Birth Date: {', '.join(result['properties']['birthDate'])}")
                if 'caption' in result:
                    print(f"  Caption: {result['caption']}")
                print("---")
        else:
            print(f"No results found for '{query_name}'.")

    except requests.exceptions.HTTPError as http_err:
        print(f"HTTP error occurred: {http_err}")
    except requests.exceptions.ConnectionError as conn_err:
        print(f"Connection error occurred: {conn_err}")
    except requests.exceptions.Timeout as timeout_err:
        print(f"Timeout error occurred: {timeout_err}")
    except requests.exceptions.RequestException as req_err:
        print(f"An error occurred: {req_err}")

if __name__ == "__main__":
    # Example search for a common name that might appear on watchlists
    search_entity("Vladimir Putin")
    print("\n---")
    search_entity("John Doe") # Example for a name with no expected matches

This Python script queries the OpenSanctions API for entities matching a given name. It prints the name, schema, ID, birth date (if available), and a short caption for each found entity. For more advanced queries, filtering, and data retrieval options, refer to the OpenSanctions API reference documentation.