Create a new transcription request
Submits audio for asynchronous transcription and optional evaluation. Provide either voice_file or voice_url. Use reference_id to correlate the result with your own call or recording ID. If webhook_url is provided, the API sends the completed transcript, session identifiers, evaluation results, and processed timestamp to that URL; webhook_header_token is sent as a bearer token in the webhook request.
Documentation Index
Fetch the complete documentation index at: https://developers.mindhunters.ai/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Use a Bearer token to access these API endpoints. Example: "Bearer {your-token}"
Body
Audio file to transcribe (max 128MB)
URL to audio file
"https://example.com/audio.mp3"
Expected language of the audio
10"en"
Context about the conversation
"Customer support call"
External reference ID
255"CALL-12345"
Customer's voice URL for reference
Human agent email. If this email matches a real user in our system, we will link the transcription to that user account.
255"agent@example.com"
Customer's phone number. The system will first check if a contact with this phone number exists and automatically assign that contact to the transcription. If no contact found by phone, it will check customer_email.
255"+1234567890"
Customer's email address. The system will check if a contact with this email exists (if not found by phone first) and automatically assign that contact to the transcription.
255"customer@example.com"
Webhook URL to receive completion notification. When transcription is completed, we will POST the results to this URL.
"https://example.com/webhook"
Token to be sent as 'Bearer {token}' in Authorization header when calling your webhook
"token123"
UUID of the QA agent template to use. If omitted, the system will fall back to default selection.
"153580ac-af27-4c77-aa59-02e9f9b8fe1a"
UUID of the coaching agent template to use. If omitted, the system will fall back to default selection.
"6d4adde3-8fb0-4893-87e1-83f950723f4e"
Response
Created
Indicates whether the request completed successfully. True for successful responses; false for documented error responses.
true
Human-readable response message. Safe to display in logs or simple client notifications; use structured fields for program logic.
"Transcription request submitted successfully"
