Lusha Signals are real-time intelligence events that surface meaningful changes happening to your contacts and target accounts. Instead of manually monitoring your CRM for stale data or researching accounts one by one, Signals alert you the moment something relevant happens — a contact changes jobs, a company raises funding, a key hire is made, or a target account shows signs of growth or risk.
How Signals Fit Your Workflow
Signals allow you to automate your Go-To-Market (GTM) strategy. Instead of reaching out to a list of accounts at random, you can set triggers to notify your sales team the moment a target account enters a "buying window."
For example, a Surge in Hiring in a specific department often signals a new budget or project, making it the ideal time for a Sales Rep to reach out with a relevant solution.
Who is Signals for?
Signals are primarily a developer and RevOps feature, accessed via the Lusha API or through the Workspace. They are most useful for:
Sales teams who want to be notified when a champion changes jobs, gets promoted, or moves to a new company.
RevOps and marketing teams who want to trigger automated workflows based on account-level events - funding rounds, new locations, hiring surges, or tech spend changes.
Developers building enrichment pipelines, CRM automation, or outreach triggers that need to react to real-world changes in contacts and companies.
Customer success teams tracking churn risk signals such as headcount decline, IT spend decrease, or key executive departures.
How Signals work
Signals are detected continuously from a range of verified data sources including LinkedIn activity, job posting data, news event monitoring, web traffic data, and IT spend indicators. Each signal represents a discrete, dated event or trend change associated with a specific contact or company.
You request signals by passing a list of contact or company IDs (or identifiers like LinkedIn URL, email, or company domain) to the Signals API. The API returns the matching signal events for each entity, covering the time period you specify.
Signals are updated on the following cadences:
Cadence | Signal types |
Daily | Website visitor tracking |
Weekly | Hiring surges, job postings, new locations, news events (financial, commercial, corporate, product, people, market intelligence, risk), job change, promotion |
Monthly | Headcount changes, website traffic changes, IT spend changes |
Accessing Signals via API
The Signals API is available at docs.lusha.com/apis/openapi/signals. Authentication requires an API key passed in the api_key header of every request. You can generate your API key at dashboard.lusha.com/enrich/api.
There are four core Signals API endpoints:
Endpoint | What it does |
Retrieve signals for a list of known contact IDs (up to 100 per request) | |
Search for contacts by LinkedIn URL, email, or name + company, and retrieve their signals in a single call | |
Retrieve signals for a list of known company IDs (up to 100 per request) | |
Search for companies by name or domain and retrieve their signals in a single call |
💡 Note: All endpoints return signals from the last 6 months by default. Use the startDate parameter (YYYY-MM-DD format) to customize the time window. Use maxResultsPerSignal to cap the number of events returned per signal type per entity.
Webhooks
Instead of polling the API, you can subscribe to real-time signal notifications using Lusha Webhooks. Webhooks deliver an HTTP POST to your endpoint the moment a signal is detected, so your workflows can react instantly without scheduled API calls.
Supports up to 25 subscriptions per bulk request
Deliveries are signed with HMAC-SHA256 for security verification
Retry logic and delivery audit logs are included
Credits are charged when a signal is delivered - retries do not incur additional charges
Full Webhooks documentation is available at docs.lusha.com/apis/openapi/webhooks.
Available signals
The tables below list every signal currently available through the Lusha Signals API, grouped by category.
Contact signals
Contact signals track changes happening to individual people. They are returned by the contact signal endpoints.
Signal | API key | Cadence | What it tells you |
Job change | companyChange | Weekly | A contact has moved to a new company. Ideal for re-engaging lapsed prospects and tracking champion moves. |
Promotion | promotion | Weekly | A contact has been promoted within their current company. Useful for identifying new decision-makers and upsell triggers. |
Growth signals
Growth signals track positive momentum at the company level — hiring, headcount expansion, traffic, and spend increases. They are returned by the company signal endpoints.
Signal | API key | Cadence | What it tells you |
Headcount increase | headcountIncrease1mheadcountIncrease3mheadcountIncrease6mheadcountIncrease12m | Monthly | Employee count has grown over the specified period. Available in 1, 3, 6, and 12-month windows. |
Surge in hiring | surgeInHiring | Weekly | Overall job posting activity has increased significantly, indicating growth mode or a major initiative. |
Hiring surge by department | surgeInHiringByDepartment | Weekly | Hiring activity has spiked in a specific department (e.g. Engineering, Sales). Useful for identifying budget holders and expansion areas. |
Hiring surge by location | surgeInHiringByLocation | Weekly | Job postings have spiked in a specific geography. Indicates market expansion or new office activity. |
New job posting | newJobPost | Weekly | A new job post has appeared in a specific department or location. Append-only; deduplicated by external job ID. |
New location | newLocation | Weekly | The company has opened a new office or expanded into a new location, detected via news events and job posting signals. |
Website traffic increase | websiteTrafficIncrease | Monthly | The company's website traffic has grown, indicating increased market interest or successful campaigns. |
IT spend increase | itSpendIncrease | Monthly | The company's estimated annual IT spend has increased, signalling technology investment and buying potential. |
Intent signals
Intent signals indicate that a company is actively researching topics relevant to your product or solution. They help you prioritise outreach to accounts that are already in-market.
Signal | API key | Cadence | What it tells you |
Intent | intent | Weekly | The company is showing above-baseline research activity around topics related to your product category, powered by Bombora B2B intent data. |
Intent by geography | intentByGeography | Weekly | Intent activity is segmented by the geographic location of the researching users within the company. |
Website visitor tracking | websiteVisitors | Daily | Anonymous website visitors from this company have been identified on your own site via the Lusha tracking pixel. See Website Visitors for setup details. |
News event signals
News event signals surface company-level events detected from business news. Each category groups related event types together. You can filter to specific event types within a category using the newsEventTypes sub-filter.
Signal | API key | Cadence | What it tells you |
Financial events | financialEventsNews | Weekly | Funding rounds, asset investments, strategic investments, IPO. Indicates capital availability and growth trajectory. |
Commercial activity | commercialActivityNews | Weekly | New partnerships, new customers, new vendors. Signals active buying and selling activity. |
Corporate strategy | corporateStrategyNews | Weekly | M&A activity, facility expansions, new locations, facility closures, asset sales, lawsuits filed. Indicates major strategic changes. |
Product activity | productActivityNews | Weekly | Product launches, product development announcements, new product integrations. Signals innovation and investment in product. |
People news | peopleNews | Weekly | Executive hires, executive departures, executive promotions, headcount changes. Key for tracking decision-maker movements. |
Market intelligence | marketIntelligenceNews | Weekly | Event participation, awards and recognition, competitor activity. Useful for timing and personalising outreach. |
Risk news | riskNews | Weekly | Security issues, lawsuits faced. Indicates instability or distraction that may affect deal timing. |
Risk signals
Risk signals flag negative trends at the account level. They are most useful for customer success teams monitoring churn risk, or sales teams qualifying accounts before investing time.
Signal | API key | Cadence | What it tells you |
Headcount decrease | headcountDecrease1mheadcountDecrease3mheadcountDecrease6mheadcountDecrease12m | Monthly | Employee count has declined over the specified period. Available in 1, 3, 6, and 12-month windows. |
Website traffic decrease | websiteTrafficDecrease | Monthly | The company's website traffic has declined, which may indicate reduced market activity or brand challenges. |
IT spend decrease | itSpendDecrease | Monthly | The company's estimated annual IT spend has fallen, signalling potential budget constraints or technology consolidation. |
Risk news | riskNews | Weekly | See News event signals above. Security issues and lawsuits are also surfaced here as risk indicators. |
Recommendations
Recommendations are not signals in the traditional sense — they do not track a discrete event. Instead, they use Lusha's matching algorithm to surface similar contacts or companies based on your existing data, and are returned on demand via a separate API endpoint.
Type | API endpoint | What it returns |
Lookalike contacts | Contacts similar in role, seniority, and industry to a given contact or list of contacts | |
Lookalike companies | Companies with similar firmographics and characteristics to a given company or list of companies |
Full documentation can be found here.
Credits and billing
Credits are charged when signal data is successfully returned. Each signal type requested counts independently towards credit usage.
Contact signals - credits are charged per contact per signal type returned
Company signals - credits are charged per company per signal type returned
Webhooks - credits are charged when a signal is detected and delivered to your endpoint; retries do not incur additional charges
Lookalikes - credits are charged per successful lookalike result returned
💡 Note: The creditCharged field in every API response shows exactly how many credits were consumed by that request.
Getting started
1. Generate your API key at dashboard.lusha.com/enrich/api.
2. Review the full API reference at docs.lusha.com/apis/openapi/signals.
3. Use the Get Signal Options endpoint (GET /api/signals/filters/{objectType}) to retrieve the full list of available signal keys for contacts or companies before building your first request.
4. Start with a small batch of contact or company IDs to validate your integration before scaling up.