> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lusha.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Search Conversations
> Search the sales conversations recorded by Lusha Conversations for your account. Returns each conversation's metadata, AI summary, action items, risks, objections, competitor mentions, coaching analysis, and chapters. Transcripts are not included - fetch those from [Get Conversation Transcript](#operation/getConversationTranscript).
**Two modes on the same contract:**
- **Keyword mode** - supply `query` to rank conversations by transcript content. All other filters are ignored.
- **Filter mode** - omit `query` and supply the structural filters.
Both modes return the same response shape. An empty body is valid and returns the first page of the account's conversations.
**Validation notes:**
- `companyDomains` matches on domain, not display name. Resolve a company name to a domain first (e.g. via [Search Companies](#operation/searchCompanies)).
- `dateFrom` / `dateTo` accept date-only `YYYY-MM-DD` values. Datetimes, reduced precision (`2026`, `2026-01`), basic format (`20260101`), and impossible dates (`2026-02-31`) are rejected with `400`.
- `pageSize` above 100 is rejected with `400` - it is not silently clamped.
- `conversationIds` that don't exist, are still processing, or belong to another account are omitted from the response rather than erroring.
> **Billing:** 1 credit per block of up to 25 conversations returned (1–25 = 1, 26–50 = 2, 51–75 = 3, 76–100 = 4), via `ci_meeting_data_export`. Charged on results returned, not the page size requested. A request that returns nothing is free. While `ci_meeting_data_export` isn't seeded on your account's pricebook, the endpoint stays free (`billing.creditsCharged` is `0`).
> **Note:** `summary`, `coaching`, and `chapters` come from an asynchronous post-call pipeline. A `null` summary on a recent conversation means analysis isn't ready yet, not "nothing found". A `null` `severity` on a risk or objection means the pipeline didn't assess it - do not read it as "low".
## OpenAPI
````yaml /openapi.json post /v3/account/conversations/search
openapi: 3.0.3
info:
title: Lusha API Documentation
version: 0.0.1
x-logo:
url: https://www.lusha.com/logo.png
license:
name: Proprietary
url: https://lusha.com/legal/terms
description: >
**This is the Lusha API V3 documentation.**
V3 introduces a new search-then-enrich pattern, bulk operations, AI-powered lookalikes, and richer filter capabilities. All endpoints are under `https://api.lusha.com/v3/`.
For more information on V3, refer to the [Migration Guide](/tutorials/v3-migration-guide).
---
Lusha provides a RESTful API for querying a comprehensive dataset of
business profiles and company information. Built for teams running
prospecting, enrichment, automation, and analytics workflows that need
accurate, continuously updated business data. The API supports both
real-time and bulk use cases.
Use the Lusha API to **search for new prospects**, **enrich existing
records**, **react to real-world changes**, and **expand coverage** with
AI-powered lookalike recommendations.
> All API requests must be made over **HTTPS**. All responses are returned
in **JSON** format.
---
## Available Endpoints
| Category | Description |
|---|---|
| [**Search**](#tag/Search) | Find contacts or companies using known
identifiers |
| [**Enrich**](#tag/Enrich) | Retrieve full profile data for contacts or
companies by ID |
| [**Search & Enrich**](#tag/Search-and-Enrich) | Find and retrieve full
contact or company data in a single call |
| [**Prospecting**](#tag/Prospecting) | Filter-based search across contacts
and companies |
| [**Lookalikes**](#tag/Lookalikes) | AI-powered recommendations for similar
contacts and companies |
| [**Buying Group**](#tag/Buying-Group) | Identify decision makers,
champions, and end users within target accounts |
| [**Contacts Tables**](#tag/Contacts-Tables) | Persist, organize, and
enrich contacts in reusable tables |
| [**Companies Tables**](#tag/Companies-Tables) | Persist, organize, and
enrich companies in reusable tables |
| [**Signals**](#tag/Signals) | Real-world activity data for contacts and
companies |
| [**Website Visitors**](#tag/Website-Visits) | Companies ranked by
website-visit signals for your tracked domains |
| [**Conversations**](#tag/Conversations) | Search recorded sales
conversations and fetch their transcripts |
| [**Filters**](#tag/Filters) | Discover valid filter values for prospecting
|
| [**Webhooks**](#tag/Webhooks) | Real-time signal notifications via HTTP
callbacks |
| [**Account**](#tag/Account) | Usage, credits, rate limits, and pricing |
**Waterfall Reveal for Contact Enrichment.**
Enrich Contacts now supports `waterfallEnabled`. Fall through to your enabled third-party providers when Lusha's own data has no match, for extra reach on hard-to-match contacts. On by default once your account has it turned on - pass `waterfallEnabled: false` to opt a specific call out. [See Enrich Contacts](#operation/enrichContacts).
---
## Data Source and Privacy
**Lusha is a search platform.** The data provided is not created or directly
managed by Lusha. It is sourced from publicly available information and
trusted business partners.
For more details on how we collect and handle data, see our [Privacy
Policy](https://lusha.com/legal/privacy-notice/).
---
## Legal Notices
(a) Data brokers and other third-party platforms may not embed, expose, or
otherwise provide access to the Lusha API, or to Data obtained through it,
on or through their own website, product, or service, without Lusha's prior
written consent.
(b) Data obtained through the API may not be used to train or develop AI/ML
systems, subject to the terms and exceptions outlined in the [Terms and
Conditions](https://lusha.com/legal/terms).
---
## Authentication
All API requests require an **API key** linked to your Lusha account and
plan. Pass your key in the `api_key` request header on every call.
> Generate and manage your API key in the [Lusha
dashboard](https://dashboard.lusha.com/enrich/api).
Store your API key securely and use it only in **server-side environments**.
---
## Rate Limiting
Lusha enforces rate limits on a per-plan basis to ensure fair usage and
platform stability. Limits are applied across multiple time windows (per
minute, per hour, and per day), and vary depending on your account plan.
Rate limits for the **Credit Usage API** differ from standard endpoint
limits.
> **Note:** To check your current plan's limits, visit the [Lusha Help
Center](https://info.lusha.com/en/articles/163856-all-there-is-to-know-about-lusha-s-api)
or contact your account manager.
**Rate Limit Response Headers**
| Header | Description |
|--------|-------------|
| `x-rate-limit-daily` | Total requests allowed per day |
| `x-daily-requests-left` | Requests remaining in your daily quota |
| `x-daily-usage` | Requests made in the current daily period |
| `x-rate-limit-hourly` | Total requests allowed per hour |
| `x-hourly-requests-left` | Requests remaining in your hourly quota |
| `x-hourly-usage` | Requests made in the current hourly period |
| `x-rate-limit-minute` | Total requests allowed per minute |
| `x-minute-requests-left` | Requests remaining in the current minute window
|
| `x-minute-usage` | Requests made in the current minute window |
---
## Error Codes
Lusha uses standard HTTP status codes to indicate the result of each
request.
| Code | Name | Description |
|------|------|-------------|
| `200` | OK | Request was successful |
| `400` | Bad Request | Request is malformed or missing required fields |
| `401` | Unauthorized | API key is missing or invalid |
| `402` | Payment Required | Insufficient credits or payment needed |
| `403` | Forbidden | Account is inactive. Contact support@lusha.com |
| `404` | Not Found | Endpoint or resource does not exist |
| `429` | Too Many Requests | Rate limit or daily quota exceeded |
| `451` | Unavailable For Legal Reasons | Request blocked due to GDPR
regulations |
| `499` | Client Closed Request | Request timed out before completing |
| `5XX` | Server Error | Issue on Lusha's end. Retry with exponential
backoff |
**Error Response Format**
```json
{
"statusCode": 400,
"message": "Invalid request parameters"
}
```
**Tables-specific error codes**
| Code | Status | Meaning |
|---|---|---|
| `TABLE_NOT_FOUND` | 404 | The `table_id` does not exist or is not
accessible to this account |
| `COLUMN_NOT_FOUND` | 404 | The `column_id` does not exist on the given
table |
| `TABLE_NAME_CONFLICT` | 409 | A table with this name already exists |
Tables error bodies use the shape `{ "message": "...", "code": , ...
}` rather than the `statusCode`/`errors` shape used elsewhere in this doc.
**Limits:** up to 500 entity IDs per add/remove call · max 50,000 entities
per table · max 500 tables per account · `page` 0–100 · `size` default 100.
**Tips for Handling Errors**
- Verify your API key is correct and active
- Read the `message` field for specific troubleshooting details
- For `429` errors, wait before retrying
- For `5XX` errors, use exponential backoff before retrying
contact:
name: Lusha Support
url: https://api.lusha.com
email: support@lusha.com
termsOfService: https://lusha.com/legal/terms
x-privacy-policy:
name: Privacy Policy
url: https://lusha.com/legal/privacy-notice/
servers:
- url: https://api.lusha.com
description: Production server
security:
- ApiKeyAuth: []
tags:
- name: Search
description: >
**Search APIs:** Find contacts or companies using known identifiers.
Look up contacts by `id`, `linkedinUrl`, `email`, or `firstName` +
`lastName` + `companyName`/`companyDomain`. Look up companies by `id`,
`name`, or `domain`.
Returns a non-PII preview of each profile with a `has` field listing
available data points and a `canReveal` field showing what can be unlocked
via Enrich.
> **Billing:** Charged per successful result via the `api_search` action.
x-tag-expanded: true
- name: Enrich
description: >
**Enrich APIs:** Retrieve full profile data for contacts or companies by
ID.
Pass IDs from Search results to reveal emails, phones, and full
firmographic data.
> **Billing:** Charged per revealed field via per-datapoint pricing
(`revealEmail`, `revealPhone`, `reveal_company`).
x-tag-expanded: true
- name: Search & Enrich
description: >
**Search & Enrich APIs:** Find and retrieve full contact or company data
in a single call.
Combines Search and Enrich into one request. Provide identifiers and
control what gets revealed via the `reveal` field. Premium data points are
never returned unless you request them explicitly in `reveal`.
> **Billing:** Two charges apply - one for the search (`api_search`) and
one per revealed field.
x-tag-expanded: true
- name: Prospecting
description: >
**Prospecting APIs:** Filter-based search for contacts and companies.
Use prospecting to find new records that match your Ideal Customer Profile
(ICP). Apply rich filters across:
- **Contact attributes:** title, seniority, location, signals
- **Company attributes:** size, revenue, industry, technologies, intent
Pass `tableId` to also persist matching results into an existing table.
See [Contacts Tables](#tag/Contacts-Tables) or [Companies
Tables](#tag/Companies-Tables).
> **Billing:** Uses the capture/charge model with `api_search` actions.
Signal charges apply additionally.
x-tag-expanded: true
- name: Lookalikes
description: >
**Lookalike APIs:** Use AI-powered recommendations to discover contacts
and companies similar to your best existing customers. The Contact
Lookalikes and Company Lookalikes endpoints return paginated results you
can pipe directly into Enrich for full data.
Pass `tableId` to also persist matching results into an existing table.
See [Contacts Tables](#tag/Contacts-Tables) or [Companies
Tables](#tag/Companies-Tables).
x-tag-expanded: true
- name: Buying Group
description: >
**Buying Group API:** Identify and prioritize the buying committee within
a set of target companies.
Supply up to 25 companies by `domain` or Lusha company `id`. The model
scores and labels each returned contact with a persona role -
`decision_maker`, `potential_champion`, or `end_user` - so you can
prioritize outreach across the buying committee instead of working one
contact at a time.
Results are lightweight previews grouped by company. Use [Enrich
Contacts](#operation/enrichContacts) with the returned `id` to reveal
emails and phones.
> **Billing:** Charged per contact returned via the `buyingGroupContact`
action.
x-tag-expanded: true
- name: Contacts Tables
description: >
**Contacts Tables API:** Create and manage persistent tables of contacts
inside Lusha.
Tables are spreadsheets with configurable columns - default Lusha fields,
enrichment data, Signals, AI insights, premium data points, CRM fields,
and custom fields. Populate a table directly through the endpoints below,
or pass `tableId` on Prospecting, Enrich, Signals, or Lookalike calls to
persist those results automatically.
Every surface that touches table data - this API, MCP, and the Workspace
UI - reads and writes the same underlying data. Changes made through one
surface are reflected on the others.
**Working with tables:**
- **Tables** - create, list, get status, update
(rename/archive/visibility), delete
- **Entities** - add, remove, or read the rows in a table
- **Columns** - browse the Lusha column catalog, add columns, list,
remove, or run a column across a table's rows
**Owner resolution:** `owner.email` resolves to a user on your account and
determines table ownership. **Required on every call when authenticating
with an API key** - omitting it returns `400`. Optional for OAuth/token
callers, since the caller is already identified by the token. Sent in the
body as `owner: { email }` on `POST`/`PATCH` calls (and on `DELETE
.../entities`, which carries a body); sent as a `?email=` query parameter
on other `GET`/`DELETE` calls, which have no body.
**Billing:**
- Adding contacts to a table is free.
- Reading entities (`GET .../entities`) charges per row returned.
- Create / List / Get / Update / Delete / Column Catalog / Add Columns /
List Columns / Remove Column / Remove Entities are free. (Add Columns is
free today - credits aren't charged for it yet.)
- Running a column charges per row per the column's tier (contact
enrichment per row with data; signal/AI/score per row per run).
- Non-public-API-plan accounts always resolve to `0` credits charged.
**Limits:** up to 500 entity IDs per add/remove call · max 50,000 entities
per table · max 500 tables per account.
See also: [Companies Tables](#tag/Companies-Tables).
x-tag-expanded: true
- name: Companies Tables
description: >
**Companies Tables API:** Create and manage persistent tables of companies
inside Lusha.
Tables are spreadsheets with configurable columns - default Lusha fields,
enrichment data, Signals, AI insights, premium data points, CRM fields,
and custom fields. Populate a table directly through the endpoints below,
or pass `tableId` on Prospecting, Enrich, Signals, or Lookalike calls to
persist those results automatically.
Every surface that touches table data - this API, MCP, and the Workspace
UI - reads and writes the same underlying data. Changes made through one
surface are reflected on the others.
**Working with tables:**
- **Tables** - create, list, get status, update
(rename/archive/visibility), delete
- **Entities** - add, remove, or read the rows in a table
- **Columns** - browse the Lusha column catalog, add columns, list,
remove, or run a column across a table's rows
**Owner resolution:** `owner.email` resolves to a user on your account and
determines table ownership. **Required on every call when authenticating
with an API key** - omitting it returns `400`. Optional for OAuth/token
callers, since the caller is already identified by the token. Sent in the
body as `owner: { email }` on `POST`/`PATCH` calls (and on `DELETE
.../entities`, which carries a body); sent as a `?email=` query parameter
on other `GET`/`DELETE` calls, which have no body.
**Billing:**
- Adding companies to a table charges `reveal_company` per **newly added**
company, deduped so duplicates and already-present companies aren't
charged again.
- Reading entities (`GET .../entities`) charges per row returned.
- Create / List / Get / Update / Delete / Column Catalog / Add Columns /
List Columns / Remove Column / Remove Entities are free. (Add Columns is
free today - credits aren't charged for it yet.)
- Running a column charges per row per the column's tier (company
enrichment once per company per table - re-runs on an already-paid company
are free; signal/AI/score per row per run).
- Non-public-API-plan accounts always resolve to `0` credits charged.
**Limits:** up to 500 entity IDs per add/remove call · max 50,000 entities
per table · max 500 tables per account.
See also: [Contacts Tables](#tag/Contacts-Tables).
x-tag-expanded: true
- name: Signals
description: >
Real-world activity data for contacts and companies.
Signals are available as standalone endpoints or as an optional `signals`
filter on Search and Prospecting endpoints.
**Contact signal types:** `promotion`, `companyChange`, `allSignals`
----
**Company signal types:** `headcountIncrease1m/3m/6m/12m`,
`headcountDecrease1m/3m/6m/12m`, `surgeInHiring`,
`surgeInHiringByDepartment`, `surgeInHiringByLocation`,
`websiteTrafficIncrease`, `websiteTrafficDecrease`, `itSpendIncrease`,
`itSpendDecrease`, `riskNews`, `commercialActivityNews`,
`corporateStrategyNews`, `financialEventsNews`, `peopleNews`,
`marketIntelligenceNews`, `productActivityNews`, `allSignals`
----
**Signal Score:** Use [Score Companies by Signal
Activity](#operation/getCompanySignalScores) or [Score Contacts by Signal
Activity](#operation/getContactSignalScores) to get a single aggregate
momentum score ([0,1]) plus the active signal breakdown for a batch of
entities, rather than a raw event list.
----
Credits are charged per matched signal per result via `showSignalsContact`
or `showSignalsCompany`.
Pass `tableId` to also persist matching results into an existing table.
See [Contacts Tables](#tag/Contacts-Tables) or [Companies
Tables](#tag/Companies-Tables).
x-tag-expanded: true
- name: Website Visits
description: >
Retrieve companies ranked by website-visit signals for your tracked
domains.
Domains must be configured for tracking in the dashboard. Each result combines a V3 company firmographic preview with behavioral visit metrics (score, sessions, unique visitors, avg session length, and more).
x-tag-expanded: true
- name: Conversations
description: >
**Conversations API:** Search the sales conversations recorded by Lusha
Conversations for your account, and fetch speaker-attributed transcripts.
Search Conversations returns each conversation's metadata, AI summary,
action items, risks, objections, competitor mentions, coaching analysis,
and chapters - transcripts are not included. Fetch the transcript for a
single conversation separately.
**Two search modes on one contract:**
- **Keyword mode** - supply `query` to rank conversations by transcript
content. All other filters are ignored.
- **Filter mode** - omit `query` and supply the structural filters (dates,
contact names, company domains, meeting titles).
Only conversations belonging to your account whose post-call processing
has completed are returned. `summary`, `coaching`, and `chapters` come
from an asynchronous pipeline and are `null`/empty until it has run - a
`null` summary means "analysis not ready yet", not "nothing found".
> **Billing:** Search charges 1 credit per block of up to 25 conversations
returned (via `ci_meeting_data_export`); a request that returns nothing is
free. Transcript charges 1 credit per successful request (via
`ci_transcript_analysis`); a `404` is never charged. While the relevant
action isn't yet seeded on your account's pricebook, the endpoint stays
free (`billing.creditsCharged` is `0`).
x-tag-expanded: true
- name: Filters
description: >
**Filter APIs:** Retrieve available filter values for prospecting.
Use the discovery endpoints to list all available filter types, then fetch
valid values for a specific filter type before building a prospecting
request.
**Contact filter types:** `departments`, `seniority`,
`existingDataPoints`, `countries`, `locations`
**Company filter types:** `names`, `sizes`, `revenues`, `locations`,
`sics`, `naics`, `industriesLabels`, `intentTopics`, `technologies`
x-tag-expanded: true
- name: Webhooks
description: >
Subscribe to real-time notifications when contacts change jobs or
companies experience key business events.
Webhooks deliver HTTP POST requests to your endpoints when signals occur -
from promotions and job changes to company growth.
> For a full list of available signals, refer to [**Signal
Options**](https://docs.lusha.com/apis/openapi/signals/getsignaloptions).
---
**Key Features:**
- Real-time contact & company signal notifications
- Bulk subscription management (up to 25 items per request)
- Secure delivery with HMAC-SHA256 signatures
- Delivery monitoring with audit logs
**Available Endpoints:**
| Method | Endpoint | Purpose |
|--------|----------|---------|
| POST | `/api/subscriptions` | Create subscriptions (bulk supported) |
| GET | `/api/subscriptions` | List all subscriptions |
| GET | `/api/subscriptions/{id}` | Get subscription by ID |
| PATCH | `/api/subscriptions/{id}` | Update subscription |
| POST | `/api/subscriptions/delete` | Delete subscriptions (bulk
supported) |
| POST | `/api/subscriptions/{id}/test` | Test subscription delivery |
| GET | `/api/audit-logs` | Get webhook delivery logs |
| GET | `/api/audit-logs/stats` | Get delivery statistics |
| GET | `/api/account/secret` | Get account webhook secret |
| POST | `/api/account/secret/regenerate` | Regenerate account secret |
| POST | `/api/subscriptions/opt-out` | Subscribe to contact opt-out
notifications |
> **Webhook Delivery Acknowledgment:** When receiving webhook deliveries
(POST requests), your endpoint must acknowledge with a specific response
format. See the [Create Subscription](#operation/createSubscription)
endpoint for the required acknowledgment structure.
---
Rate Limits
| Operation | Limit |
|-----------|-------|
| API Requests | 100 requests/minute per account |
| Create Subscriptions | 25 items per request |
| Delete Subscriptions | 25 items per request |
---
Security & Verification
**HTTPS Requirement:**
- Production webhook URLs **must** use HTTPS
- HTTP URLs are not accepted
**Signature Verification:**
All webhook deliveries include an `X-Lusha-Signature` header containing an
HMAC-SHA256 signature. Verify this signature to ensure the request is from
Lusha:
1. Extract the `X-Lusha-Signature` and `X-Lusha-Timestamp` headers
2. Concatenate: `timestamp + "." + JSON.stringify(payload)`
3. Compute HMAC-SHA256 using your webhook secret
4. Compare the computed signature with the received signature
**Example (Node.js):**
```javascript
const crypto = require('crypto');
function verifySignature(payload, signature, timestamp, secret) {
const signedPayload = `${timestamp}.${JSON.stringify(payload)}`;
const expectedSignature = crypto
.createHmac('sha256', secret)
.update(signedPayload)
.digest('hex');
return crypto.timingSafeEqual(
Buffer.from(signature),
Buffer.from(expectedSignature)
);
}
```
> **Security Best Practice:** Always verify webhook signatures to prevent
spoofed requests.
---
Credits & Billing
**Credit Charges:**
- Credits are charged when signals are detected and delivered to your
webhook
- The `creditsCharged` field in the webhook payload indicates how many
credits were used
- Credits are deducted from your account balance per signal type
**No Duplicate Charges:**
- Each signal is delivered once and charged once
- Webhook delivery retries do not incur additional charges
---
Error Response Format
All error responses follow this format:
```json
{
"statusCode": 400,
"message": "Validation failed",
"errors": ["entityType must be one of: contact, company"]
}
```
| Field | Type | Description |
|-------|------|-------------|
| `statusCode` | number | HTTP status code |
| `message` | string | Error message |
| `errors` | string[] | Detailed error messages (optional) |
---
x-tag-expanded: true
- name: Account
description: >
**Account API:** Retrieve account usage, credit balance, rate limits, plan
details, and pricing.
Use this endpoint to monitor consumption and understand the credit cost of
each action type in the public API flow.
> **Rate limit:** 5 requests per minute.
x-tag-expanded: true
paths:
/v3/account/conversations/search:
post:
tags:
- Conversations
summary: Search Conversations
description: >
Search the sales conversations recorded by Lusha Conversations for your
account. Returns each conversation's metadata, AI summary, action items,
risks, objections, competitor mentions, coaching analysis, and chapters.
Transcripts are not included - fetch those from [Get Conversation
Transcript](#operation/getConversationTranscript).
**Two modes on the same contract:**
- **Keyword mode** - supply `query` to rank conversations by transcript
content. All other filters are ignored.
- **Filter mode** - omit `query` and supply the structural filters.
Both modes return the same response shape. An empty body is valid and
returns the first page of the account's conversations.
**Validation notes:**
- `companyDomains` matches on domain, not display name. Resolve a
company name to a domain first (e.g. via [Search
Companies](#operation/searchCompanies)).
- `dateFrom` / `dateTo` accept date-only `YYYY-MM-DD` values. Datetimes,
reduced precision (`2026`, `2026-01`), basic format (`20260101`), and
impossible dates (`2026-02-31`) are rejected with `400`.
- `pageSize` above 100 is rejected with `400` - it is not silently
clamped.
- `conversationIds` that don't exist, are still processing, or belong to
another account are omitted from the response rather than erroring.
> **Billing:** 1 credit per block of up to 25 conversations returned
(1–25 = 1, 26–50 = 2, 51–75 = 3, 76–100 = 4), via
`ci_meeting_data_export`. Charged on results returned, not the page size
requested. A request that returns nothing is free. While
`ci_meeting_data_export` isn't seeded on your account's pricebook, the
endpoint stays free (`billing.creditsCharged` is `0`).
> **Note:** `summary`, `coaching`, and `chapters` come from an
asynchronous post-call pipeline. A `null` summary on a recent
conversation means analysis isn't ready yet, not "nothing found". A
`null` `severity` on a risk or objection means the pipeline didn't
assess it - do not read it as "low".
operationId: searchConversations
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/V3ConversationsSearchRequest'
examples:
keywordMode:
summary: Keyword mode (ranks by transcript content)
value:
query: pricing objection
page: 1
pageSize: 25
filterMode:
summary: Filter mode (structural filters)
value:
dateFrom: '2026-01-01'
dateTo: '2026-03-31'
companyDomains:
- acme.com
contactNames:
- Jane Doe
meetingTitles:
- Quarterly review
page: 1
pageSize: 25
responses:
'200':
description: Successful response
content:
application/json:
schema:
$ref: '#/components/schemas/V3ConversationsSearchResponse'
example:
requestId: 3f1a9c2e-7b4d-4a8e-9f10-2c5d6e7a8b90
conversations:
- id: 8f2c9b1e-4a7d-4f3b-9c2e-1d6a5b8c7e90
title: Acme <> Lusha - Quarterly review
date: '2026-03-12'
startTime: '2026-03-12T14:00:00Z'
durationSeconds: 1830
durationFormatted: 30m 30s
meetingType: discovery
isExternal: true
company:
name: Acme Inc
domain: acme.com
participants:
- name: Jane Doe
email: jane@acme.com
role: VP Sales
isInternal: false
- name: Sam Rep
email: sam@lusha.com
role: AE
isInternal: true
topicLabels:
- pricing
- security
summary:
text: The team walked through the pricing tiers.
keyHighlights:
- Budget confirmed for Q3
actionItems:
- text: Send the revised pricing sheet
owner: Sam Rep
dueDate: '2026-03-19'
nextSteps:
- Schedule a technical deep dive
risks:
- text: Budget approval is still pending
severity: high
objections:
- text: Price is above the current spend
severity: null
competition:
- name: Competitor Inc
context: Mentioned as incumbent
sentiment: negative
coaching:
overallScore: 68
likelihoodOfSale: 45
sections:
- section: discovery
score: 72
whatHappened: The rep opened with a clear agenda.
whatToKeep:
- Strong discovery questions
whatToImprove:
- Confirm the decision process earlier
notes: Focus on quantifying impact.
chapters:
- index: 0
title: Introductions
startTime: '00:00:00'
endTime: '00:04:12'
summary: Participants introduced themselves.
page:
page: 1
pageSize: 25
totalItems: 137
totalPages: 6
billing:
creditsCharged: 1
resultsReturned: 1
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'402':
$ref: '#/components/responses/PaymentRequired'
'403':
$ref: '#/components/responses/Forbidden'
'429':
$ref: '#/components/responses/TooManyRequests'
components:
schemas:
V3ConversationsSearchRequest:
type: object
description: >
All properties are optional. Supply `query` for keyword mode (structural
filters are then ignored), or omit `query` and supply structural filters
for filter mode. An empty body returns the first page of the account's
conversations.
properties:
query:
type: string
minLength: 1
maxLength: 500
description: >-
Free-text search over transcript content. When present, the
structural filters below are ignored.
example: pricing objection
conversationIds:
type: array
items:
type: string
minItems: 1
maxItems: 100
description: >-
Return only these conversations. IDs that don't exist, are still
processing, or belong to another account are omitted from the
response rather than erroring.
dateFrom:
type: string
format: date
description: Earliest meeting date, inclusive (YYYY-MM-DD).
example: '2026-01-01'
dateTo:
type: string
format: date
description: Latest meeting date, inclusive (YYYY-MM-DD).
example: '2026-03-31'
contactNames:
type: array
items:
type: string
description: >-
Partial, case-insensitive match on participant names. Multiple
values are ORed.
example:
- Jane Doe
companyDomains:
type: array
items:
type: string
description: >-
Company domains of the external participants (e.g. acme.com).
Matches on domain, not display name. Multiple values are ORed.
example:
- acme.com
meetingTitles:
type: array
items:
type: string
description: >-
Partial, case-insensitive match on the meeting title. Multiple
values are ORed.
example:
- Quarterly review
page:
type: integer
minimum: 1
default: 1
description: Page number, starting at 1.
example: 1
pageSize:
type: integer
minimum: 1
maximum: 100
default: 25
description: >-
Conversations per page. Values above 100 are rejected with 400 (not
silently clamped).
example: 25
V3ConversationsSearchResponse:
type: object
properties:
requestId:
type: string
format: uuid
description: Correlation / request id for support and tracing.
example: 3f1a9c2e-7b4d-4a8e-9f10-2c5d6e7a8b90
conversations:
type: array
description: >-
Matching conversations. In keyword mode they are ordered by content
relevance.
items:
$ref: '#/components/schemas/Conversation'
page:
$ref: '#/components/schemas/ConversationPage'
billing:
$ref: '#/components/schemas/V3Billing'
Conversation:
type: object
properties:
id:
type: string
description: Conversation identifier. Pass this to Get Conversation Transcript.
example: 8f2c9b1e-4a7d-4f3b-9c2e-1d6a5b8c7e90
title:
type: string
description: Meeting title.
example: Acme <> Lusha - Quarterly review
date:
type: string
format: date
description: Meeting date (YYYY-MM-DD).
example: '2026-03-12'
startTime:
type: string
format: date-time
description: Meeting start time (ISO 8601).
example: '2026-03-12T14:00:00Z'
durationSeconds:
type: number
description: Meeting length in seconds.
example: 1830
durationFormatted:
type: string
description: Human readable length, e.g. 30m 30s.
example: 30m 30s
meetingType:
type: string
nullable: true
description: Meeting type as classified by the analysis pipeline.
example: discovery
isExternal:
type: boolean
nullable: true
description: true when at least one participant is outside your account.
example: true
company:
$ref: '#/components/schemas/ConversationCompany'
participants:
type: array
items:
$ref: '#/components/schemas/ConversationParticipant'
topicLabels:
type: array
items:
type: string
description: Topics detected in the conversation.
example:
- pricing
- security
summary:
$ref: '#/components/schemas/ConversationSummary'
coaching:
$ref: '#/components/schemas/ConversationCoaching'
chapters:
type: array
description: Timestamped chapters. Empty until the analysis pipeline has run.
items:
$ref: '#/components/schemas/ConversationChapter'
ConversationPage:
type: object
description: Paging envelope for Search Conversations.
properties:
page:
type: integer
example: 1
pageSize:
type: integer
example: 25
totalItems:
type: integer
example: 137
totalPages:
type: integer
example: 6
V3Billing:
type: object
description: Credit usage summary for a V3 API request
properties:
creditsCharged:
type: integer
description: Total credits charged for this request
example: 3
resultsReturned:
type: integer
description: Number of successful results returned
example: 1
ErrorResponse:
type: object
required:
- statusCode
- message
properties:
statusCode:
type: integer
description: HTTP status code
example: 400
message:
type: string
description: Error message
example: Validation failed
errors:
type: array
items:
type: string
description: Detailed error messages (optional, only for validation errors)
example:
- 'entityType must be one of: contact, company'
ConversationCompany:
type: object
description: External participants' company. Either field may be null.
properties:
name:
type: string
nullable: true
example: Acme Inc
domain:
type: string
nullable: true
example: acme.com
ConversationParticipant:
type: object
properties:
name:
type: string
example: Jane Doe
email:
type: string
example: jane@acme.com
role:
type: string
example: VP Sales
isInternal:
type: boolean
example: false
ConversationSummary:
type: object
nullable: true
description: Post-call analysis, or null while it is still being produced.
properties:
text:
type: string
description: Narrative summary.
example: The team walked through the pricing tiers.
keyHighlights:
type: array
items:
type: string
description: Notable moments.
example:
- Budget confirmed for Q3
actionItems:
type: array
items:
$ref: '#/components/schemas/ConversationActionItem'
nextSteps:
type: array
items:
type: string
example:
- Schedule a technical deep dive
risks:
type: array
items:
$ref: '#/components/schemas/ConversationSeverityItem'
objections:
type: array
items:
$ref: '#/components/schemas/ConversationSeverityItem'
competition:
type: array
items:
$ref: '#/components/schemas/ConversationCompetitor'
ConversationCoaching:
type: object
nullable: true
description: Coaching analysis, or null while it is still being produced.
properties:
overallScore:
type: number
description: Overall coaching score, 0–100.
example: 68
likelihoodOfSale:
type: number
nullable: true
description: Predicted likelihood of closing, 0–100. May be null.
example: 45
sections:
type: array
items:
$ref: '#/components/schemas/ConversationCoachingSection'
notes:
type: string
description: Free-text coaching notes.
example: Focus on quantifying impact.
ConversationChapter:
type: object
properties:
index:
type: integer
example: 0
title:
type: string
example: Introductions
startTime:
type: string
description: Offset from the start of the recording.
example: '00:00:00'
endTime:
type: string
description: Offset from the start of the recording.
example: '00:04:12'
summary:
type: string
example: Participants introduced themselves.
ConversationActionItem:
type: object
properties:
text:
type: string
example: Send the revised pricing sheet
owner:
type: string
example: Sam Rep
dueDate:
type: string
format: date
nullable: true
description: May be null.
example: '2026-03-19'
ConversationSeverityItem:
type: object
properties:
text:
type: string
example: Budget approval is still pending
severity:
type: string
nullable: true
description: >-
Null means the pipeline did not assess severity. Do not read it as
"low".
example: high
ConversationCompetitor:
type: object
properties:
name:
type: string
example: Competitor Inc
context:
type: string
example: Mentioned as incumbent
sentiment:
type: string
nullable: true
description: May be null.
example: negative
ConversationCoachingSection:
type: object
properties:
section:
type: string
example: discovery
score:
type: number
nullable: true
description: May be null.
example: 72
whatHappened:
type: string
example: The rep opened with a clear agenda.
whatToKeep:
type: array
items:
type: string
example:
- Strong discovery questions
whatToImprove:
type: array
items:
type: string
example:
- Confirm the decision process earlier
responses:
BadRequest:
description: Bad request - invalid input data
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
statusCode: 400
message: Invalid request parameters
Unauthorized:
description: Unauthorized - invalid or missing API key
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
statusCode: 401
message: Invalid API key
PaymentRequired:
description: Payment required - insufficient credits
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
statusCode: 402
message: Insufficient credits for this operation
Forbidden:
description: >-
Forbidden - account inactive, V3 access not enabled, or plan does not
include this feature
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
accountInactive:
summary: Account inactive
value:
statusCode: 403
message: >-
Your account is not active. Please reach out to support at
support@lusha.com
v3NotEnabled:
summary: V3 access not enabled
value:
statusCode: 403
message: V3 API access is not enabled for your account
TooManyRequests:
description: Too many requests - rate limit exceeded
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
example:
statusCode: 429
message: Too many requests. Please wait before making another request.
headers:
x-rate-limit-daily:
description: Total requests allowed per day
schema:
type: integer
x-daily-requests-left:
description: Requests remaining in daily quota
schema:
type: integer
x-rate-limit-hourly:
description: Total requests allowed per hour
schema:
type: integer
x-hourly-requests-left:
description: Requests remaining in hourly quota
schema:
type: integer
x-rate-limit-minute:
description: Total requests allowed per minute
schema:
type: integer
x-minute-requests-left:
description: Requests remaining in current minute window
schema:
type: integer
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: api_key
description: >
Your Lusha API key. You can find this in your Lusha dashboard under API
settings.
Include this key in the `api_key` header for all requests.
````