Server URLloading...

POST

/api/v1/call-imports/audio-upload

Send

Authorization

Header

Body

Persist manually uploaded recordings as completed CallImport rows.

The rows skip the provider-download worker entirely because the audio bytes are already in hand. From this point onward they behave exactly like completed CSV-import rows: playback reads recording_s3_key and the existing diarisation/evaluation endpoints can operate on them.

Header Parameters

Response Body

curl -X POST "https://example.com/api/v1/call-imports/audio-upload" \  -F files="[    \"string\"  ]" \  -F dataset="string"

{  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",  "total_rows": 0,  "status": "pending",  "dataset": "string",  "tags": [    {      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",      "name": "string",      "color": "string",      "created_at": "2019-08-24T14:15:22Z",      "updated_at": "2019-08-24T14:15:22Z"    }  ],  "message": "string"}