Retrieve contact signals for job changes and promotions

Contact signals tell you when someone in your pipeline or CRM has changed jobs or received a promotion. One endpoint takes up to 100 Lusha contact IDs and the signal types you want, and returns everything that matched - no separate lookup or search step.

Signals are charged per matched signal per result. Request only the signal types you need.

Signal types for contacts

Signal type	Description
`allSignals`	All available contact signal types
`promotion`	Job title promotions within the same company
`companyChange`	Moves to a new employer

Call Get Contact Signal Types to fetch this list programmatically instead of hardcoding it.

Get contact signals

POST https://api.lusha.com/v3/contacts/signals

Send 1–100 Lusha contact IDs per request along with the signalTypes you want. Use startDate to limit results to signals detected on or after a given date, and maxResultsPerSignal to cap how many instances of each signal type come back per contact. Request body

Field	Type	Required	Description
`ids`	array of strings	Yes	Lusha contact IDs, 1–100 per request
`signalTypes`	array of strings	Yes	Signal types to retrieve: `allSignals`, `promotion`, `companyChange`
`startDate`	string	No	Earliest date for signals, in `YYYY-MM-DD` format
`maxResultsPerSignal`	integer	No	Maximum signal instances returned per type per contact (1–100)

Example request

{
  "ids": ["4389064624", "4389064654"],
  "signalTypes": ["allSignals"],
  "startDate": "2025-01-01"
}

Example response

{
  "results": [
    {
      "id": "4389064624",
      "companyChange": [],
      "promotion": []
    }
  ],
  "startDate": "2025-01-01",
  "endDate": "2025-07-31",
  "billing": {
    "creditsCharged": 2,
    "resultsReturned": 1
  }
}

Matched events for each requested signal type appear directly on the result under that type’s key (promotion, companyChange) - there’s no wrapper object to unpack.

If you don’t have contact IDs yet

Contact Signals only accepts Lusha contact IDs. If you’re starting from a LinkedIn URL, email, or name, resolve the contact first, then retrieve signals for the returned ID:

Resolve the contact

Call Enrich Contacts or Search & Enrich Contacts to get a Lusha contact id.

Retrieve signals for that ID

Pass the id into POST /v3/contacts/signals.

Signals overview - the consolidated signals model, credits, and delivery options
Company signals - retrieve signals for companies
API reference: Contact Signals - full request/response schema

Overview

Resources

Endpoints

Retrieve contact signals for job changes and promotions

Signal types for contacts

Get contact signals

If you don’t have contact IDs yet

​Signal types for contacts

​Get contact signals

​If you don’t have contact IDs yet

​Related pages

Signal types for contacts

Get contact signals

If you don’t have contact IDs yet

Related pages