Gowajee API
  • Introduction
  • Getting Started
  • Speech to text
    • Models
    • Limitations
      • Rate Limit
      • Astro Model Limitation
      • Word Timestamp
      • Words Boosting
      • Audio Duration Limit
      • Handling Large Files
      • HTTP Multipart/Form-Data
      • Supported File Formats
    • Transcription
      • Synchronous API (Request-Response)
      • Asynchronous API (Webhook Notification)
        • Checking Job Status
    • Real-time Transcription
    • Speaker Separation
      • Multichannel
      • Diarization
    • Words Boosting
    • Raw Audio Format
  • Pricing
Powered by GitBook
On this page
  • Using Presigned URLs
  • Example Request with pre-signed URL:
  1. Speech to text
  2. Limitations

Handling Large Files

PreviousAudio Duration LimitNextHTTP Multipart/Form-Data

Last updated 11 months ago

When sending requests with audioData, you need to encode the audio file into format and include it in the request. However, for large file sizes or long-duration audio files, Gowajee supports using to avoid encoding the file data to base64

Using Presigned URLs

To transcribe large or long-duration files, you can use a . By providing the in the audioData field instead of base64 encoded data, our API will automatically download the audio file from the provided URL and process the transcription.

Example Request with pre-signed URL:

POST /v1/speech-to-text/${MODEL}/transcribe HTTP/1.1
Host: api.gowajee.ai
Content-Type: application/json
X-Api-Key: ${YOUR_API_KEY}

{
  "audioData": "https://example.com/presigned_url_to_audio_file"
}

Notes

  • Base64 Encoding: Ensure the audio data is base64 encoded if you are not using Presigned URLs.

  • Presigned URLs: Use Presigned URLs for large files or long-duration audio to optimize performance and avoid base64 encoding overhead.

Base64
Pre-signed URLs
pre-signed URL
pre-signed URL