Synchronous API Documentation, SalesCallFollowUpPack

Synchronous API: AI Sales Call Follow-up Pack

Use direct execution only when the HTTP client can wait for local media preparation, transcription and follow-up generation.

curl --location --request POST 'https://mxprocess.com/api/files/start-process' \
--header 'Authorization: Bearer YOUR_JWT' \
--form 'actionName=SalesCallFollowUpPack' \
--form 'file=@sales-call.mp3' \
--form 'parameters=[["language",["English"]],["sellerCompany",["Terra Medium"]],["salesObjective",["prepare proposal follow-up"]]]' \
--form 'async=false'

A successful response contains salesCallFollowUpPack and downloadResults. The JSON deliverables are attachments in downloadResults; they must be downloaded as files, never interpreted as AJAX response data.

{"output":{"salesCallFollowUpPack":{"title":"Sales follow-up"},"downloadResults":[["sales-call-follow-up-pack.json","https://storage.example/..."]]},"0":{"id":123,"accomplished":true}}

Functional error example

{"error":"ERROR_SCFP008 AI Sales Call Follow-up Pack found no intelligible speech."}

For queued processing, use the asynchronous API.