Run Column on Contacts Table
Populate or refresh a column’s data for some or all rows in the table. This is asynchronous - the call returns immediately with status: "processing"; poll Get Contacts Table for isProcessing and per-column row-status counts to know when it’s done, then read the values via Get Contacts Table Entities.
runScope values:
all- every row, including already-processed ones (re-runs / refreshes). Most expensive.missing- only rows that have never been run for this column. Cheapest, safe to call repeatedly.specific- only theentityIdsyou pass. Also how you implement “run for this page” - fetch the page via Get Contacts Table Entities, then pass those IDs here.
Billing: Charged per row processed, per the column’s credit tier. Re-running with
allcharges again for rows that already have data.
Authorizations
Your Lusha API key. You can find this in your Lusha dashboard under API settings.
Include this key in the api_key header for all requests.
Body
Controls which rows a column operation applies to. all re-runs every row, including already-processed ones. missing only runs rows that don't have a value for this column yet. specific requires entityIds.
all, missing, specific Identifies the user acting on the table, and resolves to a user on your account. Required on every table-route call when authenticating with an API key (there is no signed-in user) - omitting it returns 400. Optional for OAuth/token callers, since the caller is already identified by the token; still accepted if you want to act on behalf of another owner.
Required when runScope is specific.