Skip to main content
POST
Add Entities to Contacts Table

Authorizations

api_key
string
header
required

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

table_id
string
required

The table's ID.

Body

application/json
entityIds
string[]
required

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.

Maximum array length: 500
Example:
owner
object
required

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.

companyIds
string[]

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.

Example:

Response

Entities added

data
object
billing
object

Credit usage summary for a V3 API request