Skip to main content
POST
Get or generate transcription for an audio file
Retrieves the transcription for a given file. If no transcription exists in the system, and a valid audioUrl is provided, a new transcription will be generated and stored.

Request

Headers

Path Parameters

Parameter Details

  • fileId: Must be a valid file identifier in the system
  • Used to lookup existing transcriptions or store new ones

Request Body

Request Body Schema

Field Details

  • audioUrl: Required only if no existing transcription is found
  • Must be a publicly accessible URL
  • Supports common audio formats (mp3, wav, m4a, etc.)
  • Used to generate new transcription when none exists

Response

200 OK - Successfully retrieved or generated transcription

400 Bad Request

404 Not Found

500 Internal Server Error

Examples

Get existing transcription

Generate new transcription

Data Fields Explained

Transcription Data

Segments Array

Use Cases

  • Call Center Analytics: Analyze customer service calls
  • Meeting Transcriptions: Transcribe meeting recordings
  • Content Creation: Convert audio content to text
  • Accessibility: Provide text alternatives for audio content
  • Search and Analysis: Enable text search in audio content

Implementation Examples

React Transcription Component

Audio Player with Transcription Sync

Transcription Status Polling

Best Practices

  1. Error Handling: Handle transcription failures gracefully
  2. Progress Feedback: Show progress indicators for long transcriptions
  3. Audio Formats: Use supported audio formats for best results
  4. URL Validation: Validate audio URLs before submission
  5. Caching: Cache transcriptions to avoid reprocessing

Performance Considerations

  • Processing Time: Transcription can take time for long audio files
  • File Size: Large audio files may hit size limits
  • Concurrent Requests: Limit concurrent transcription requests
  • Storage: Consider storage costs for transcriptions
  • Use /transcription/{fileId} to delete transcriptions
  • Use audio upload endpoints to upload files for transcription
  • Use user management endpoints to manage transcription permissions

Notes

  • Transcription quality depends on audio quality and clarity
  • Processing time varies with audio length and complexity
  • Generated transcriptions are stored for future retrieval
  • Speaker diarization may be available for multi-speaker audio
  • Language detection is automatic but can be specified if needed

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

fileId
string
required

Unique identifier of the audio file.

Example:

"670fcae25abf2d8e5c8a4a12"

Body

application/json
audioUrl
string

URL of the audio file used for transcription (required only if no existing transcription is found).

Example:

"https://example.com/uploads/audio-file.mp3"

Response

Successfully retrieved or generated transcription

message
string
Example:

""

data
object