RuPEP Public Database of PEPs in Russia and Belarus

RuPEP is a detailed database of politically exposed persons in Russia and Belarus maintained by qualified researchers

From the RuPEP site:

The database of public officials of Russia (PEP, Politically exposed person) – is the database created for financial monitoring subjects (banks, payment organizations, exchanges, etc.) in order to detect Russian PEP and its related persons, and to assess the level of risk associated with servicing such clients.

The site is public and free to use for non-commercial purposes if it references to the site.

Financial monitoring subjects can also obtain information from the database in JSON or XML format and receive regular updates for financial monitoring purposes.

The use of information obtained from this site for further resale in the form of various analytical products or for other commercial purposes is prohibited. The exception is the use of information by journalists, public figures and analysts to prepare materials for the media, scientific research, etc.

Data overview

Entity types:
41 countries · Show overview...

The group maintaining this database is not publicly identified. The OpenSanctions team is happy to create introductions for those interested in the commercial reuse of the material.

Source data:rupep.org (JSON)
Collections:in Due Diligence List · Politically Exposed Persons (PEPs)
Last changed:

Bulk download

Downloads contain the full set of entities contained in this dataset. You can fetch a simplified tabular form, or detailed, structured data in JSON format. Updated files will be provided once a day at the same location.

File nameExport typeSize
entities.ftm.jsonFollowTheMoney entities29 MB
names.txtTarget names text file4 MB
targets.nested.jsonTargets as nested JSON40 MB
targets.simple.csvTargets as simplified CSV3 MB

Help: Using the data · format reference · identifier use · commercial licensing

Using the API

You can query the data in this dataset via the application programming interface (API) endpoints below. Please read the introduction for documentation and terms of service. See also: OpenAPI Specification (JSON)

Use the Reconciliation API in OpenRefine:
For full-text search, use the /search endpoint:
For entity matching, use the /match endpoint: