CEcekura
observability

POST /observability/v1/call-logs/create_scenarios/

Changed on

Generate test scenarios from real production call logs.

Returns a progress_id immediately — the actual scenario creation runs in the background. Poll GET /observability/v1/call-logs/create_scenarios_progress?progress_id=<id> until completed_scenarios + failed_scenarios >= total_scenarios. The scenarios_list field (full Scenario objects) is populated only once processing is complete.

call_logs accepts: a list of IDs [1, 2, 3] or "all" for every call log on the agent.

copy_to_agent: optionally copy the generated scenarios to a different agent — useful when your observation agent and your test agent are separate.

Prerequisite: call logs must have a transcript (uploaded via transcript_json). Audio-only logs without a transcript cannot produce scenarios.

Deprecated: POST /observability/v3/call-logs/create_scenarios/ does this in one call and returns the result.

Request

  • Base URL
    https://api.cekura.ai
  • URL
    https://api.cekura.ai/observability/v1/call-logs/create_scenarios/
  • Auth
    • API key in header X-CEKURA-API-KEY
    • or HTTP bearer
    • or HTTP bearer
    • or HTTP bearer

Request body

agent_idinteger

Agent ID, required if assistant_id is not provided Example: 2142

assistant_idstring

Assistant ID, required if agent_id is not provided Example: asst_1234567890

call_logsinteger[]

List of call log IDs to create scenarios from. Can also be the string "all" to process all call logs. Example: [1, 2, 3] or "all"

copy_to_agentinteger nullable

Optional agent ID to copy created scenarios to Example: 2142

project_idinteger

Project ID. Required when using folder_path. Example: 1376

folder_pathstring nullable

Folder path to assign the created scenarios to. Example: "Sales.Inbound"

Response

progress_idstring uuid

Unique identifier for tracking the progress of scenario creation

Changes