The Signals API delivers real-time business changes - like job moves, promotions, and hiring surges - directly into your existing workflows. Instead of relying on static contact records, you get live triggers that tell you exactly when to reach out and why.
How is this different from regular enrichment?
Standard enrichment fills in contact details: name, title, email. Signals tell you when something has changed - a past buyer joined a new company, a decision-maker got promoted, or a target account is hiring fast. That timing is what makes outreach land.
Key features
Multiple input types - contact IDs, email addresses, LinkedIn URLs, or company domains.
Signal filtering - request only the signal types you need.
Timeframe control - filter by start and end date. The default window is the last 6 months.
Consistent output - every response includes a person_id or company_id for easy CRM matching.
Authentication - API key-based.
Rate limits - standard public API limits apply. Learn more here
Who is this for?
RevOps leaders - automate CRM updates, improve lead scoring, and reduce manual data work.
BDRs - know exactly when to reach out and with what context.
Credits
1 credit per contact or company enrichment.
1 credit per 25 search results
Get started
Explore Signal Enrichment Templates β Pre-built templates to get your first Signals API workflow running fast.
Buying Signals Plays on Lusha Campus β ready-to-run workflows built by experts, which you can use as-is or adapt to fit your setup
Available signals
Signal type | Level | What does it tells you |
Job Change | Contact | A contact has moved to a new company |
Promotion | Contact | A contact has been promoted |
Surge in Hiring | Company | A company is posting roles for key initiatives |
Headcount Increase | Company | A company's team is growing |
Commercial Activity News | Company | New partnerships or customer activity |
Corporate Strategy News | Company | M&A, new locations, facilities expansion |
Financial Events News | Company | Funding rounds, IPOs, investment activity |
Market Intelligence News | Company | Shifts in market positioning |
People News | Company | Leadership and workforce changes |
Product Activity News | Company | Product launches, updates, integrations |
Risk News | Company | Legal or security flags |
π‘ Note: Surge in Hiring was previously called "New Job Listing." Headcount Increase was previously called "Headcount Growth."
Learn more about Signals by exploring our API Signals documentation, or the Understanding Signals API article.
API endpoints
Endpoint | What it does |
/signals/contacts | Enrich a list of contacts by contact ID |
/signals/companies | Enrich a list of companies by company ID |
/signals/contacts/search | Find and enrich contacts by email, LinkedIn URL, or other identifiers |
/signals/companies/search | Find and enrich companies by name, domain, or other identifiers |
/signals/filters/:objectType | View all available signal filter options for contacts or companies |
How a search call works
Request - /signals/contacts/search
{
"contacts": [
{
"id": "123321",
"social_link": "https://www.linkedin.com/in/ron-nabet"
}
],
"signals": [
"promotion",
"companyChange"
],
"startDate": "2025-01-01"
}Response - /signals/contacts/search
{
"contacts": {
"123321": {
"personId": "115889",
"companyChange": [
{
"currentCompanyName": "Callaway Golf",
"currentTitle": "Senior Manager, IT Solutions",
"signalDate": "2025-05-01",
"previousCompanyName": "Previous Corp",
"previousDomain": "nextgen.com",
"currentDomain": "vendavo.com"
}
],
"promotion": [
{
"currentCompanyName": "Callaway Golf",
"currentTitle": "Senior Manager, IT Solutions",
"signalDate": "2025-05-01"
}
]
}
},
"endDate": "2025-07-31",
"startDate": "2025-01-01",
"creditCharged": 2
}
Use cases
Re-engage past buyers who changed companies - Track job change signals for contacts in your CRM. When a past buyer moves to a new company, trigger a personalized outreach sequence automatically.
Reach new leaders during their first 90 days - Promotion signals surface decision-makers right after they step into new roles - when they're most open to evaluating new tools and building their tech stack.
Route high-growth accounts to sales faster - Headcount Increase signals identify companies in expansion mode. Route those accounts to your team before competitors do.
Spot companies hiring around your use case - Surge in Hiring signals let you identify companies posting roles that signal a need for your product - and position your solution as the answer to the challenge they're hiring to solve.
Build real-time lead scoring - Feed signals directly into your scoring model. Contacts showing multiple active signals - such as a promotion and a company change - automatically rise to the top.
Build churn early warning systems - When a decision-maker at a customer account changes jobs, alert your CSM team so they can reach out before the renewal is at risk.
Continue learning by Understanding Signals API .
π οΈ FAQs
Q: How is this different from regular enrichment or intent data?
A: Regular enrichment fills in static contact details. Intent data infers interest from browsing behavior. Signals surface real, verified business changes β a promotion, a job move, a hiring spike. They give you a specific reason to reach out at a specific moment.
Q: Do I need a developer to set this up?
A: Not necessarily. The Signals API works with no-code tools like Make, Zapier, and n8n. Full documentation is available at docs.lusha.com.
Q: How accurate is the data?
A: Signals are built on Lusha's verified, structured data. They're refreshed weekly and validated across multiple sources.
Q: What if I'm already using an enrichment tool?
A: Static enrichment keeps your contact records current. Signals add a time dimension - they tell you when something relevant has changed, so you can act on it.
Q: Is the Signals API GDPR compliant?
A: Yes. The API is built with GDPR compliance in mind. Contact-level signals are tied to publicly available career updates only, and data access is scoped and secure.