Skip to main content
POST
Contact Signals

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.

Body

application/json
ids
string[]
required
Required array length: 1 - 100 elements
Example:
signalTypes
enum<string>[]
required
Available options:
allSignals,
promotion,
companyChange
Example:
startDate
string<date>
Example:

"2025-01-01"

maxResultsPerSignal
integer
Required range: 1 <= x <= 100
Example:

10

tableId
string

Optional. If provided, these contacts are also added to this table (if not already present) and the Signals column is populated. See the Tables API.

Example:

"482910"

Response

Successful response

results
object[]
startDate
string
endDate
string
tableWrite
object

Added to a Prospecting, Enrich, Signals, or Lookalike response when tableId is passed on the request. The primary response is unaffected even if the table write fails.

billing
object

Credit usage summary for a V3 API request

requestId
string<uuid>

Request ID, for support and tracing