Skip to main content
The Conversations API exposes the sales calls recorded by Lusha Conversations to your own tooling. Search across the account’s conversations, then pull the full transcript for any one of them. It’s two endpoints working together: search returns everything about a conversation, and a second call returns what was actually said.

Search Conversations

POST /v3/account/conversations/search - metadata, summaries, and analysis.

Get Conversation Transcript

GET /v3/account/conversations/{conversationId}/transcript - the speaker-attributed transcript.

​
Two search modes on one contract

Search Conversations behaves differently depending on whether you supply query: Both modes return the same response shape. An empty body is valid and returns the first page of the account’s conversations.
In keyword mode the structural filters are ignored rather than combined. If you need both a text match and a date range, filter the results client-side.

​
Filter-mode fields

​
What search returns

Each conversation comes back with its metadata plus AI-derived analysis: summary, action items, risks, objections, competitor mentions, coaching analysis, and chapters. Transcripts are not included.
summary, coaching, and chapters come from an asynchronous pipeline and are null or empty until it has run. A null here means “not processed yet”, not “nothing found”. Only conversations whose post-call processing has completed are returned at all.

​
Fetching a transcript

Take a conversationId from search and call the transcript endpoint. There’s no request body and no query parameters.
1

Find the conversation

Call POST /v3/account/conversations/search in either mode and pick the conversation you want.
2

Fetch the transcript

Call GET /v3/account/conversations/{conversationId}/transcript to get the speaker-attributed, timestamped transcript.
A single 404 covers all three failure cases: the conversation doesn’t exist, its processing hasn’t completed, or it belongs to another account.
Transcripts can be long. If you’re feeding one to an LLM, budget for the token count or summarize before passing it through.

​
Billing

While ci_transcript_analysis isn’t seeded on your account’s pricebook, the transcript endpoint stays free.