Skip to main content
POST
Contact Signals
Use this endpoint when you already have Lusha contact IDs and want their signal activity - promotions and company changes - in one call. Pass up to 100 ids and the signalTypes you want back; there is no separate “search” step in V3 - one call returns all matched signal data for the IDs you send.
Don’t have Lusha contact IDs yet? Resolve contacts first with Enrich Contacts or Search & Enrich Contacts, then pass the returned id values here.

Endpoint

Authentication: API key (ApiKeyAuth)

Request body

string[]
required
Lusha contact IDs to retrieve signals for. 1–100 items per request.Example: ["4389064624", "4389064654"]
string[]
required
Signal types to retrieve.Allowed values: allSignals, promotion, companyChangeUse allSignals to retrieve every available contact signal type in one call.
string
Limit results to signals detected on or after this date, in YYYY-MM-DD format.Example: "2025-01-01"
integer
Maximum number of signal instances to return per signal type per contact. Range: 1–100.Example: 10

Example request


Response

200 - Success

object[]
One entry per requested contact ID.
string
The start date used for this request.
string
The end date used for this request (the request date, unless you’re querying historical data).
object
Credit usage summary for this request.
Billing: Charged per matched signal per result via the showSignalsContact action.

Error codes

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