Skip to main content
POST
Company 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,
linkedinActivityIntent,
websiteTrafficDecrease,
websiteTrafficIncrease,
itSpendIncrease,
itSpendDecrease,
surgeInHiring,
headcountIncrease1m,
headcountIncrease3m,
headcountIncrease6m,
headcountIncrease12m,
headcountDecrease1m,
headcountDecrease3m,
headcountDecrease6m,
headcountDecrease12m,
surgeInHiringByDepartment,
surgeInHiringByLocation,
riskNews,
commercialActivityNews,
corporateStrategyNews,
financialEventsNews,
peopleNews,
marketIntelligenceNews,
productActivityNews
Example:
startDate
string<date>

For linkedinActivityIntent, results are limited to a trailing 90-day window regardless of the value passed (legal requirement). Other signal types are unaffected.

Example:

"2025-01-01"

maxResultsPerSignal
integer

For linkedinActivityIntent, results are capped at 50 per company regardless of the value passed. Other signal types use the requested value as-is (1-100).

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

10

tableId
string

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

Example:

"583021"

filters
object

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