> ## Documentation Index > Fetch the complete documentation index at: https://docs.wavix.com/llms.txt > Use this file to discover all available pages before exploring further. # Retrieve a transcription > Returns the transcription for the request identified by `request_id`, including transcript, speaker turns, and insights when available. ## OpenAPI ````yaml https://wavix.github.io/wavix-openapi/wavix-api.yaml get /v1/speech-analytics/{request_id} openapi: 3.1.0 info: title: Wavix APIs description: >- Wavix provides robust APIs that let you integrate voice and text messaging features directly into your app. Send text, place calls, and access detailed reports programmatically. termsOfService: https://wavix.com/terms-and-conditions license: name: MIT identifier: MIT contact: name: Wavix url: https://wavix.com email: support@wavix.com version: '1.0' servers: - url: https://api.wavix.com description: https://api.wavix.com variables: {} security: - bearerAuth: [] tags: - name: SIP trunks description: SIP trunks - name: Buy description: Numbers - name: Cart description: Numbers - name: My numbers description: Numbers - name: Billing description: Billing, transactions, and invoices - name: Profile description: Account profile and customer information - name: CDRs description: Call detail records and call history - name: Speech Analytics description: Call transcription and speech analytics - name: SMS and MMS description: Messaging - name: Number Validator description: Phone number validation - name: Link shortener description: Short link and click metrics - name: 2FA description: Two-factor authentication - name: 10DLC description: 10DLC Campaigns and Brands - name: API Keys description: API key management - name: Call webhooks description: Webhook configuration for call events - name: Call control description: Programmable Voice - name: Call streaming description: Real-time call audio streaming over WebSocket - name: Call recording description: Call recording - name: Sub-accounts description: Sub-account management - name: Voice campaigns description: Outbound voice campaigns - name: Wavix Embeddable description: WebRTC embeddable widget paths: /v1/speech-analytics/{request_id}: get: tags: - Speech Analytics summary: Retrieve a transcription description: >- Returns the transcription for the request identified by `request_id`, including transcript, speaker turns, and insights when available. operationId: speech_analytics_get parameters: - name: request_id in: path description: >- The `request_id` of the transcription, returned when the file was uploaded. required: true style: simple schema: type: string example: e865ea07-25af-4fdd-876e-04b0d41d5ebd responses: '200': description: Returns the completed transcription. headers: {} content: application/json: schema: allOf: - $ref: '#/components/schemas/FileTranscriptionResponse' - example: transcript: channel_1: Hi there channel_2: Hello turns: - speaker: channel_1 s: 600 e: 700 text: Hi sentiment: positive request_id: e84f350f-6da7-4b56-80eb-41dec572626b language: en duration: 102 charge: '0.01' status: completed transcription_date: '2023-01-09T10:04:39.734Z' transcription_score: '3.8' transcription_summary: >- The agent and client discussed call recording and call transcription original_file: https://api.wavix.com/v1/files/uuid examples: success: summary: Successful response value: transcript: channel_1: Hi there channel_2: Hello turns: - speaker: channel_1 s: 600 e: 700 text: Hi sentiment: positive request_id: e84f350f-6da7-4b56-80eb-41dec572626b language: en duration: 102 charge: '0.01' status: completed transcription_date: '2023-01-09T10:04:39.734Z' transcription_score: '3.8' transcription_summary: >- The agent and client discussed call recording and call transcription original_file: https://api.wavix.com/v1/files/uuid '202': description: Accepted. The transcription is still in progress. headers: {} content: application/json: schema: type: object properties: success: type: boolean description: Indicates whether the request was accepted. example: true message: type: string description: Human-readable status message. example: The transcription is still pending examples: default: value: success: true message: The transcription is still pending '404': $ref: '#/components/responses/NotFoundErrorResponse' deprecated: false security: - bearerAuth: - calls:read components: schemas: FileTranscriptionResponse: title: FileTranscriptionResponse required: - transcript - turns - request_id - language - duration - charge - status - transcription_date - transcription_score - transcription_summary - original_file type: object additionalProperties: false properties: transcript: description: Complete transcription text attributed to each channel. oneOf: - $ref: '#/components/schemas/FileTranscriptResponse' - type: 'null' turns: type: - array - 'null' items: $ref: '#/components/schemas/FileTranscriptTurn' description: >- List of transcription turns, including speaker attribution, timestamps, and sentiment. example: - speaker: channel_1 s: 600 e: 700 text: Hi sentiment: positive request_id: type: string description: Transcription request ID. example: e84f350f-6da7-4b56-80eb-41dec572626b language: allOf: - $ref: '#/components/schemas/TranscriptionLanguage' - description: Transcription language. example: en duration: type: - integer - 'null' description: File duration in seconds. format: int32 example: 102 charge: type: string description: Total transcription charge in USD. example: '0.01' status: allOf: - $ref: '#/components/schemas/TranscriptionStatus' - description: Transcription status. Possible values are `completed`, `failed`. example: completed transcription_date: type: string description: Date and time of the transcription in ISO 8601 format. format: date-time example: '2023-01-09T10:04:39.734Z' transcription_score: type: - string - 'null' description: >- Conversation sentiment score. Scores from 1.0 to 3.0 are negative; scores from 4.0 to 5.0 are positive. example: '3.8' transcription_summary: type: - string - 'null' description: Transcription summary. example: The agent and client discussed call recording and call transcription original_file: type: string description: Uploaded file URL. example: https://api.wavix.com/v1/files/uuid FileTranscriptResponse: title: FileTranscriptResponse required: - channel_1 - channel_2 type: object additionalProperties: false properties: channel_1: type: string description: Transcription of speaker one. example: Hi there channel_2: type: string description: Transcription of speaker two. example: Hello FileTranscriptTurn: title: FileTranscriptTurn required: - speaker - s - e - text - sentiment type: object additionalProperties: false properties: speaker: type: string description: Speaker identifier. example: channel_1 s: type: integer description: Turn start time in milliseconds from the beginning of the file. format: int32 example: 3000 e: type: integer description: Turn end time in milliseconds from the beginning of the file. format: int32 example: 18000 text: type: string description: Transcription text attributed to the speaker. example: Hi there, how are you? sentiment: type: string description: >- Sentiment associated with the turn. Possible values are `positive`, `neutral`, `negative`. example: positive description: >- Transcription `turn` details, including speaker, timestamps, text, and sentiment. example: speaker: channel_1 s: 600 e: 700 text: Hi there sentiment: positive TranscriptionLanguage: title: TranscriptionLanguage enum: - en - de - es - fr - it - null type: - string - 'null' description: >- Language of the transcription, as a two-letter ISO 639-1 code. One of `en` (English), `de` (German), `es` (Spanish), `fr` (French), or `it` (Italian). `null` lets the platform auto-detect the language. TranscriptionStatus: title: TranscriptionStatus enum: - completed - failed type: string description: >- Outcome of the transcription. One of `completed` (the transcript was produced) or `failed` (the transcription could not be produced). NotFoundErrorResponse: title: NotFoundErrorResponse type: object properties: success: type: boolean description: >- Indicates whether the request was successful. Always `false` for this error. example: false message: type: string description: >- Human-readable description stating that no resource matches the given ID. example: Record not found responses: NotFoundErrorResponse: description: Request failed. An object with the specified ID is not found. headers: {} content: application/json: schema: $ref: '#/components/schemas/NotFoundErrorResponse' securitySchemes: bearerAuth: type: http scheme: bearer description: > Wavix API key. Pass as `Authorization: Bearer `. Keys support per-resource scopes (none / read / write). See [Restricted keys and scopes](https://docs.wavix.com/api-reference/authentication#restricted-keys-and-scopes). ````