Changelog

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

## [1.7.0] - 2026-01-26 - Webhooks API Release

### Added

**New Webhooks API**  
Introduced real-time event notifications for contact and company signals via webhooks.

#### POST /subscriptions
- Create webhook subscriptions to receive real-time notifications for:
  - **Contact signals**: Job changes, promotions, and career events
  - **Company signals**: Headcount growth, new job openings, news events, and business updates
- Configure webhook endpoints to receive event payloads automatically
- Manage multiple subscriptions with custom filters and event types

#### GET /subscriptions
- List all active webhook subscriptions
- View subscription configuration and status

#### GET /subscriptions/{subscriptionId}
- Retrieve details for a specific webhook subscription
- Monitor subscription health and delivery status

#### PUT /subscriptions/{subscriptionId}
- Update existing webhook subscription settings
- Modify event types, filters, and webhook endpoints

#### DELETE /subscriptions/{subscriptionId}
- Remove webhook subscriptions when no longer needed

### Features
- **Real-time Delivery**: Receive instant notifications when signals occur
- **Event Filtering**: Subscribe to specific signal types (promotion, job change, headcount growth, etc.)
- **Webhook Security**: Includes signature verification for secure payload validation
- **Retry Logic**: Automatic retry mechanism for failed webhook deliveries
- **Event History**: Track webhook delivery status and payload history

### Notes
- Webhooks provide a push-based alternative to polling the Signals API
- Ideal for time-sensitive workflows like triggering outreach on job changes
- Reduces API calls by receiving only relevant updates as they happen
- Works in conjunction with the existing Signals API for detailed signal metadata
- Premium feature — standard credit charges apply for signal detection

---
## [1.6.0] - 2025-01-05 - Prospecting API Signal Filtering

### Added

**Signal Filtering for Prospecting Search**  
Enhanced Prospecting APIs with signal-based filtering capabilities.

#### POST /prospecting/contact/search
- Can now filter contacts by signal types:
  - `promotion`
  - `companyChange`
  - `allSignals`

#### POST /prospecting/company/search
- Can now filter companies by signal types:
  - `headcountGrowth`
  - `newJobsOpen`
  - `newsEvent`
  - `allSignals`

#### Temporal Filtering
- Added a `startDate` parameter to enable time-based filtering of signals.

#### Response Enhancements
- Search responses now return a `signalTypes` array, indicating the detected signals for each contact or company.

### Changed

- **Prospecting Search Response**
  - Added `signalTypes` field to both contact and company search results.

- **Prospecting Search Request**
  - Added a `signal` object to filter options, including:
    - `names` (array of signal types)
    - Optional `startDate`

### Notes
- This is a premium feature — credits are charged for each signal type that returns results.
- Enables targeted prospecting by identifying contacts at key career moments (e.g. promotions, job changes).
- Enables company targeting based on business events (e.g. growth, hiring activity, news).
- Works in conjunction with the existing Signals API for retrieving detailed signal metadata.
--- 

## [1.5.0] - 2025-10-15 - Recommendations API Release

### Added
- **New Recommendations Endpoints**:
  - `POST /api/recommendations/contacts` – Get AI-powered recommendations for similar contacts
  - `POST /api/recommendations/companies` – Get AI-powered recommendations for similar companies
- **Recommendations API Overview**:
  - Discover look-alike prospects based on your existing contact or company data
  - Uses AI models to surface highly relevant profiles aligned with your ICP
  - Supports workflows for prospecting expansion, upsell targeting, and account-based outreach

### Notes
- This release introduces Lusha’s first recommendation engine designed to help you scale prospecting by suggesting net-new contacts and companies with similar attributes to your known leads.
- Recommendations can be used as a downstream step after enrichment, prospecting, or CRM triggers.

## [1.4.0] - 2025-09-30 - Enhanced Search Capabilities

### Added
- **New searchText Filter**: Introduced free-text search capability for Prospecting APIs
  - Available in both `include` and `exclude` sections for contact and company filters
  - `POST /prospecting/contact/search` – Supports searchText in both `contacts` and `companies` filter sections
  - `POST /prospecting/company/search` – Supports searchText in `companies` filter section
  - Enables natural language queries like "finance marketing in Germany DE"
  - Searches across multiple fields simultaneously (names, titles, descriptions, locations)

### Changed
- **Prospecting Search Schemas**: Updated `ContactFilters` and `CompanyFilters` to include optional `searchText` property
  - Contact filters: Can search/exclude across contact names, titles, and related text fields
  - Company filters: Can search/exclude across company names, descriptions, and locations

### Notes
- The searchText filter provides a more flexible and intuitive way to search the Prospecting database
- Supports complex queries combining multiple criteria in a single text string
- Can be combined with existing structured filters for more precise targeting
- Both positive (include) and negative (exclude) text filtering is supported

## [1.3.0] - 2025-09-10 - Signals API Expansion

### Added
- **New Signals Endpoints**: Introduced 4 endpoints for contact and company signals, supporting enrichment by IDs and identifiers:
  - `POST /signals/contacts` – Retrieve contact signals by IDs
  - `POST /signals/companies` – Retrieve company signals by IDs
  - `POST /signals/contacts/search` – Retrieve contact signals by identifiers (LinkedIn URL, email, or name + company/domain)
  - `POST /signals/companies/search` – Retrieve company signals by identifiers (domain, company name, or ID)
- **Signals Filters Endpoint**:
  - `GET /signals/filters/:objectType` – View available signal filters for `contact` or `company`
  - `allFilters` option available to view all signals
- **Timeframe Filtering**: All signal endpoints support `start_date` (optional) with default range of last 6 months
- **Partial Profile Filter**: Added `partialProfile` boolean parameter to contact enrichment APIs for simplified contact profiles

### Changed
- **Enrichment APIs**: Expanded `v2/person` (single & bulk) and `v2/company` (single & bulk) to always return `person_id` and `company_id` where applicable
- **Signal Filters Usage**: Existing enrichment APIs can now leverage signals as filters

### Notes
- The new Signals suite allows deeper insights into contact and company activity
- Timeframe filtering provides flexibility while defaulting to recent (6 months) signals
- Partial profiles provide a lightweight option for basic contact information retrieval

## [Version] - YYYY-MM-DD

### Added
- New features and endpoints

### Changed  
- Updates to existing functionality

### Fixed
- Bug fixes and corrections

### Removed
- Deprecated features

### Security
- Security improvements