Import a client watchlist

Use this guide to bulk-load client, prospect, opponent or market names. Each name is matched against authority addressees, approved parties and published recitals.

#1. Prepare the list

Use CSV with a header row. Only name is required.

clients.csv

name,aliases,externalId,interest,note
Alphabet Inc.,Google|Google LLC,C-0012,client,Lead partner: A. Rahman
Acme Logistics SA,,C-0040,prospect,

Column	Required	Notes
`name`	yes	At least 3 letters or digits.
`aliases`	no	Separated by a pipe (`\|`). Up to 20.
`externalId`	no	Your own ID. Used to merge on re-import.
`interest`	no	`client`, `prospect`, `opponent` or `market`.
`note`	no	Free text.

#2. Preview the import

Always start with dryRun: true. Nothing is written.

bash

curl -s -X POST http://127.0.0.1:8787/v1/radar/watchlist/import \
  -H 'Content-Type: application/json' \
  -d "$(python3 -c "import json;print(json.dumps({'listName':'Client list','importedBy':'A. Lawyer','csv':open('clients.csv').read(),'dryRun':True}))")"

You can send a clients array of objects instead of csv. The limit is 1,000 rows per request.

#3. Apply it

Send the same body with "dryRun": false. The import is recorded as a radar.watchlist.imported event.

#4. Re-import later

Re-importing the same list merges entries by externalId, or by normalised name when there is no ID. Rows missing from the new file are not removed automatically — delete them with DELETE /v1/radar/watchlist/:id.

#5. Read alerts

bash

curl -s "http://127.0.0.1:8787/v1/radar/alerts?from=2026-07-01&to=2026-07-31" | python3 -m json.tool

Each alert keeps its evidence path and source hash. Repeated ingests do not duplicate alerts.

In the console, the same flow is under Client radar → Import a client list.