NOnoso
Transcription

Transcribe audio with new recording system (Celery-based)

Called by mobile app after S3 upload completes to trigger transcription.

Expected flow:

  1. Mobile calls /recordings/upload-started → creates recording with status='uploading'
  2. Mobile uploads audio to S3
  3. Mobile calls this endpoint → updates to status='transcribing' and queues Celery task
post/tools/transcribe_v3

Request

  • Base URL
    https://api.noso.so (the document declares no server; this is the origin it was published from)
  • URL
    https://api.noso.so/tools/transcribe_v3
  • Auth
    HTTP bearer

Request body

bucketstring required
object_keystring required
task_idstring required
speaker_labelsboolean
streaming_transcribe_textstring nullable
location_latnumber nullable
location_lngnumber nullable
location_accuracynumber nullable
start_timestampinteger nullable
end_timestampinteger nullable

Example request

{
  "bucket": "your-s3-bucket-name",
  "end_timestamp": 1704067800,
  "location_accuracy": 10,
  "location_lat": 37.7749,
  "location_lng": -122.4194,
  "object_key": "recordings/audio-file.wav",
  "speaker_labels": true,
  "start_timestamp": 1704067200,
  "streaming_transcribe_text": "Real-time transcription content from frontend",
  "task_id": "your-task-id"
}

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 23 revisions of this API.