Custom data exports
Some systems need the data in a particular shape: one row per name, a fixed set of columns, or only some registers. This page explains what you can produce yourself today and how to ask us for an export built to your specification.
Exports we offer
We do not yet publish ready-made custom exports (for example, a PEP file with one row per position, or a wide file with numbered columns).
Single registers
Each register cleared for download can be exported on its own, as CSV or JSON lines, from its page in the source register or from the API:
GET /api/export?source=<register name>&format=csv|jsonl
# example
curl "https://api.crownintelligence.net/api/export?source=OFAC%20SDN&format=csv"
Columns: id, name, alt_names, list_type, entity_type, program, dob, nationality, entity_id, first_seen, loaded_at, source. See Downloads and the endpoint reference.
Building your own layout
The bulk files carry everything needed to derive most layouts. Two examples with jq:
# one row per name (primary and aliases) with id, type and register
jq -r '. as $e | ($e.properties.name + ($e.properties.alias // []))[]
| [$e.id, $e.schema, ., $e.datasets[0]] | @csv' targets.nested.json > names-by-record.csv
# PEP records with their role text, one row per listing
jq -r 'select(.properties.topics | index("role.pep")) | . as $e | $e.properties.sanctions[]
| [$e.id, $e.caption, ($e.properties.birthDate // [""])[0], (.properties.program // [""])[0], .properties.authority[0]]
| @csv' targets.nested.json > peps-roles.csv
Or load statements.csv into a database and pivot it: every value is a row there, with its record, property and register.
Asking for an export
Tell us the layout, the registers or topics, the format and how often you need it. Write to [email protected] or use Talk to sales.
Last updated 2026-10-03