Add Entities to Contacts Table
Add up to 500 contact IDs to an existing table. entityIds accepts either the encrypted Lusha token (v{N}.…, as returned by Search/Enrich/Get Entities) or the legacy numeric personId - an ID that’s neither returns 400. Already-present IDs are reported as alreadyPresent and not re-added; unresolvable IDs are not an error, they come back in invalidIds with a 200.
Optionally pass companyIds - one lushaCompanyId per contact, index-aligned with entityIds - to help pair company-level enrichment to the right company for each contact.
Billing: Free.
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.
Path Parameters
The table's ID.
Body
Lusha IDs as strings - personId for contacts, lushaCompanyId for companies. Accepts either the encrypted token (v{N}.…, as returned by Search/Enrich/Get Entities) or the legacy numeric ID. An ID that is neither a valid token nor numeric returns 400.
500Identifies 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.
Contacts tables only. One lushaCompanyId per contact (encrypted token or numeric), index-aligned with entityIds, to help pair company-level enrichment to the right company for each contact. Ignored on companies tables.