Create Call
Ingest a completed call for analysis.
Accepts the transcript and metadata for a call that has already finished. Tuner queues it
for evaluation; scores, outcomes, and red flags appear on the call record shortly after.
call_id must be unique: re-sending an already-ingested call returns a conflict.
Authorizations
Query Parameters
Body
Request schema for public call creation.
The call timeline in chronological order. Each item is a user turn, an agent turn, a tool call or its result, or a workflow node transition.
User and agent turns must carry timing — as words, as start_ms and end_ms, or as start_ms and duration_ms. Latency and voice metrics are computed from it.
1Public https URL of the call recording (audio file or provider recording link). Required. A value that isn't a public https URL (e.g. a placeholder such as pending) is stored as sent but treated as no recording: it isn't played back or used for Dataset calls.
1 - 1024Optional SIP headers from the incoming call. For Tuner simulation calls, pass back the X-Correlation-Id header Tuner sent to link the call to its simulation. Only the X-Correlation-Id (or Correlation-Id) header is kept, and it is used only to link the call to its simulation; all other headers are ignored.
Custom data about the call, as a JSON object. Nested objects are allowed and keys are case-sensitive. ai_models and usage_token have a defined structure; any other keys are accepted. Merged with general_meta_data_raw, whose keys win on collision. Evals, rules and alerts can refer to these keys as metadata.<key>: in an eval's inputs_used, in an alert condition, and in the key of a call_metadata rule condition.
Custom data about the call, as a JSON object. Nested objects are allowed and keys are case-sensitive. If metadata is also sent, the keys are merged and these keys win on collision. Evals, rules and alerts refer to these keys the same way as for metadata.
Supplying this opts the call into receiving a presigned upload target (recording_upload in the response) so you can upload the call's audio directly to Tuner's storage. Provide the file extension without a leading dot (e.g. 'wav', 'mp3'). Omit this field entirely if you are not uploading audio.
Whether the audio being uploaded has the caller and the agent on separate channels rather than mixed into a single channel. Only applies to audio uploaded via recording_file_extension. Omit this field if the recording is a mono mix -- it is treated as a mono mix by default.
Response
Successful Response
Response schema for public call creation.
Present only when the request set recording_file_extension and the upload target could be prepared; the target is valid for 24 hours. Null if the extension was omitted, if the call already had a recording uploaded, or if preparing the target failed after the call was otherwise saved successfully.