Lusha releases a Webhooks API for real-time contact and company signals
Lusha's API v1.7.0, released January 26, 2026, adds a Webhooks API that pushes contact and company signal events in real time, with signature verification, retries and delivery audit logs.
Lusha's January 26, 2026 changelog entry, v1.7.0, introduces a Webhooks API. Instead of polling the Signals API, customers subscribe to contact and company signal events and receive them as they occur. The release adds endpoints to manage subscriptions, send test deliveries with mock payloads at no credit cost, read delivery audit logs and statistics, and manage the shared webhook secret. Lusha suggests uses such as triggering outreach when a contact changes jobs.
The details
- Subscriptions can be created in bulk, up to 25 per request.
- Deliveries are signed with HMAC-SHA256 and retried up to three times with exponential backoff.
- Audit logs are retained for 90 days for successful deliveries and 180 days for failed ones.
- Test deliveries use mock payloads and consume no credits; retries do not incur additional charges.
- Webhooks are a premium feature with standard credit charges for signal detection.
Context
The Webhooks API was one of Lusha's first 2026 API releases, followed by expanded data fields and news signals in February and lookalike endpoints in February and March. Covered later work includes waterfall enrichment in July, Buying Group, Signal Score and Conversations APIs in September, and ICP Fit Score, intent topic and Recommendations APIs in October 2026.
Not disclosed
- Credit cost per signal event delivered by webhook
- Maximum number of active subscriptions per account
- Which plans include premium webhook access
- Vendor
Lusha- Category
- Data & Enrichment
- Announcement type
- Product release
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.




