Lusha adds a LinkedIn activity intent signal to its prospecting and signals APIs
Lusha's API v2.7.0, released August 5, 2026, adds a LinkedIn Activity Intent company signal that returns relevant LinkedIn posts with detected Bombora topics, AI-generated summaries and engagement counts.
Lusha's August 5, 2026 changelog entry, v2.7.0, adds linkedinActivityIntent as a company signal type. Customers can filter prospecting results by the signal and by intent category, or look up the signal for known companies. A new endpoint returns the full list of Bombora intent categories. Authors and mentioned people or companies are resolved to Lusha IDs where possible. The changelog describes the 90-day window as a legal limit, and the same signal type is also selectable through the allSignals option on both endpoints.
The details
- Available in POST /v3/companies/prospecting and POST /v3/companies/signals.
- Optional filters narrow results to specific Bombora intent categories.
- Each post result includes an AI-generated activitySummary and engagement counts.
- Start dates are capped to a trailing 90-day window; results are capped at 50 per company.
- Unresolved authors or mentioned entities return id: null.
Context
The LinkedIn signal extends a signals line that began with Lusha's Signals API in 2025 and the news signal expansion in February 2026. In September 2026 Lusha added a Signal Score API, and in October it added intent topic APIs, both covered by ForgeX Research. The LinkedIn signal was released eight days after Lusha's waterfall enrichment for contacts.
Not disclosed
- Credit cost per LinkedIn activity result
- How posts are collected and matched to companies
- How often the signal data is refreshed
- Vendor
Lusha- Category
- Data & Enrichment
- Announcement type
- Feature update
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.




