List Lookup

Repair the company names on every row of a Parvenu list. Asynchronous, free, writes in place.

POST /normalize_company_names_list

This is an asynchronous endpoint. It returns a job acknowledgement, not data. Poll /check_list_status until the list reports done, then fetch the rows with /download_list. Free: nothing is charged.

This writes in place, over organization_name, because that is the field every integration maps. The original is preserved in organization_name_raw and re-read on a re-run, so improvements to the rules reach rows already processed and the original is never lost.

Each row's own company_description, keywords and company_website are read as spelling sources, exactly as on the single-name route. Nothing is written to them.

Headers

Name	Value
Content-Type	application/json

Body

Name	Type	Description
api_key	string	Your API Key.
listname	string	Name of the existing Parvenu list to repair.
processing_mode	string	Optional. blank_only (default), all, or first_10.
view	string	Optional. Which rows of the list to process. all (default) processes every contact in the list; verified restricts the run to contacts whose email address is verified.
saved_view	string	Optional. Name of a saved view on this list. Runs only on the contacts in that view. Don't combine with view, filter_stack or search.

Saved views. To run only on the contacts in a saved view, send its name as saved_view. See List Saved Views.

Processing modes

Value	Behaviour
blank_only	Default. Rows never normalized before: the raw backup is still empty. Not "the name column is empty".
all	Re-processes every row, re-reading each from its raw backup.
first_10	The first 10 rows only. Use it as a bounded first look.

Example

Input

{
  "api_key": "your_api_key",
  "listname": "my_list",
  "processing_mode": "first_10"
}

Output

{
  "success": true,
  "job_id": "a1b2c3d4e5f6",
  "status": "queued",
  "list_name": "my_list",
  "rows_selected": 50,
  "rows_fetched": 50,
  "message": "Normalize company names (filtered) started",
  "view": "all",
  "max_rows": 5000,
  "credits_estimated": 0,
  "truncated": false,
  "credits_used": 0
}

Every row gets a line in its log saying what was done and why, including the rows nothing changed on.

Start with "processing_mode": "first_10" and read the results. The failure worth checking for is not a name left broken. It is a name that was already right being changed.

Retrieving results

• Check List Status

• Download List Data