Skip to main content
POST
Generate a structured summary from a completed transcription. The transcription must be in completed status. You can create multiple summaries for the same transcription using different templates. Use webhooks to receive real-time notifications when the summary completes, or poll the Get Summary endpoint.

Authentication

Requires an API key with summaries:write scope.

Request Body

transcription_id
string
required
The transcription’s unique identifier (e.g., txn_abc123). Must be in completed status.
template_id
string
System template ID to use. One of: tmpl_general_notes, tmpl_sales_call, tmpl_clinical_soap, tmpl_legal_memo.Either template_id or prompt is required, but not both.
prompt
string
Custom prompt for one-off summaries. Use this instead of template_id for custom summarization.Must be 10-10,000 characters. Either template_id or prompt is required, but not both.
provider
string
LLM provider to use for summarization. If not specified, uses the system default.

Response

Returns the newly created summary object with pending status.

Response Fields

Templates

Bota provides four built-in system templates optimized for different use cases: See Summary Templates for detailed output schemas.

Custom Prompts

For custom summarization, use the prompt parameter instead of template_id:

Summary Status

Auto-Summary

Instead of calling this endpoint manually, you can enable auto-summary to automatically generate a summary whenever a transcription completes. Configure via the hierarchical config system:
Auto-summary works with auto-transcription for a fully automated pipeline: upload → transcribe → summarize. See the Auto-Processing Guide for full details. For production use, subscribe to webhook events instead of polling: See Webhooks Overview for setup instructions.
Summary generation typically takes 5-15 seconds, depending on transcript length and template complexity.