API access

Conversation intelligence API for product teams.

Create conversation objects, retrieve source moments, run agents, and receive webhooks when conversation intelligence needs to live inside your product or tools.

Talk to founders
API workbenchreview-ready
Custom application review

Agent output can trigger an application workflow.

Webhook event
Objects438

conversation records

Agent runs96

over conversation objects

Webhooks14

workflow events

POST /v1/agent-runs200 OK
{
  "conversation_id": "conv_9j2f7",
  "agent": "custom_escalation_check",
  "source_moment": {
    "timestamp": "00:42",
    "speaker": "Workflow owner",
    "signal": "Webhook candidate"
  },
  "destinations": ["Object","Agent run","Webhook"],
  "webhook": "agent_run.completed"
}
conversation.created201

Audio reference and metadata accepted.

agent_run.completed2.4s

Cited result available for review.

workflow.triggeredsent

Destination received the mapped payload.

Async by design. Structured by default.

The API is built around queued processing, reusable conversation objects, agent runs, and webhook delivery.

01

POST /conversations

Send audio, transcript references, metadata, source system, and custom fields. Receive a conversation ID immediately.

02

GET /conversations/:id

Retrieve status, segments, speakers, timestamps, metadata, processing state, and object fields.

03

POST /agent-runs

Run Sales QC, analytics, customer, event, or custom checks over a conversation or conversation set.

04

Receive webhooks

Handle conversation.created, transcription.completed, agent_run.completed, and workflow.triggered events.

Build on the object, not raw transcripts.

Product teams use Speechrun when they need source moments, agent outputs, and workflow payloads inside their own software.

01

Conversation object

Segments, speakers, timestamps, metadata, custom fields, and processing state.

02

Agent result

Structured finding, source moment, severity, reason, destination, and review context.

03

Webhook payload

Event type, IDs, status, source moment reference, and application route context.

04

Search and retrieval

Find commitments, risks, objections, customer signals, event themes, or custom tags across conversations.

Questions about API access.

How conversation objects, agent runs, and webhooks fit into a workflow.

API access is for technical teams that want conversation objects, agent runs, and webhooks inside their own product or workflow systems.
Workflow API access
Evidence Webhook candidate
Integration Object / Agent run / Webhook

Map the API workflow behind your conversation intelligence use case.

We will define the conversation object, agent run, webhook, and integration behavior your product needs.

Talk to founders