Senzing

Each collection is also published as senzing.json, with every record mapped to the Senzing entity specification. Load it beside your own customer, supplier or vendor records and let Senzing entity resolution link them to listed parties.

The files follow Senzing's Generic Entity Specification. Download a collection and try it in your own Senzing installation; for production use you will need a commercial licence from us, in addition to whatever your Senzing installation requires.

Senzing files by collection

Collection	Description	Records	Size	File
Crown Default	All screening registers cleared for download	—	—	`senzing.json`
Consolidated sanctions	Sanctions registers	—	—	`senzing.json`
Politically exposed persons	PEP registers	—	—	`senzing.json`
Debarment and enforcement	Debarment, exclusion and enforcement registers	—	—	`senzing.json`
Maritime	Vessels and records with an IMO number	—	—	`senzing.json`

We do not publish Senzing files for single registers, or for registry reference data (company registers, LEI).

To be provided: whether we will publish Senzing files per register or for registry data, and on what terms.

Record fields

DATA_SOURCE: Always CROWN. Register this data source in Senzing before loading.
RECORD_ID: Our record id, crown-<number>, the same as in the other files.
RECORD_TYPE: PERSON for people; ORGANIZATION for everything else, vessels and aircraft included.
NAMES: The primary name (NAME_TYPE: PRIMARY) and each alias (ALIAS), as NAME_FULL for people and NAME_ORG otherwise.
DATES: DATE_OF_BIRTH, to the precision published.
COUNTRIES: NATIONALITY for people, REGISTRATION_COUNTRY otherwise; ISO codes in upper case.
IDENTIFIERS: OTHER_ID_TYPE: IMO with the seven-digit number, where we hold one.
URL: Link to the record at its publisher, where the register gives one.
RISKS: TOPIC: sanction, role.pep, debarment or reg.action.

{"DATA_SOURCE":"CROWN","RECORD_ID":"crown-380054154","RECORD_TYPE":"ORGANIZATION",
 "NAMES":[{"NAME_TYPE":"PRIMARY","NAME_ORG":"PELIKAN"},{"NAME_TYPE":"ALIAS","NAME_ORG":"BALTIC ATLANT SHPG-LITHUANIA"}],
 "IDENTIFIERS":[{"OTHER_ID_TYPE":"IMO","OTHER_ID_NUMBER":"6922169"}],
 "RISKS":[{"TOPIC":"debarment"}]}

Each line is one record (JSON lines, UTF-8). Fields we do not hold are left out rather than sent empty.

Loading the file

Download the collection's senzing.json and check it against the SHA-256 in its index.json (see checking a download).
Add a data source named CROWN to your Senzing configuration.
Load the file with Senzing's file loader, as you would any JSON-lines source.
After each new build, load the changed records again. Senzing replaces a record that has the same DATA_SOURCE and RECORD_ID; records removed from a register appear as DEL operations in delta.json and should be deleted by id.

Senzing® is a registered trademark of Senzing, Inc. Crown Intelligence is not affiliated with Senzing.

Last updated 2026-10-03