Update Scenario
Authentication
Authenticate server-side requests with a private Vapi API key. Create or copy a key from the Vapi Dashboard and send it in the Authorization header as Bearer <token>. Keep private API keys out of client-side code and public repositories.
Path parameters
Request
This is the script/instructions for the tester to follow during the simulation.
This is the structured output-based evaluation plan for the simulation. Each item defines a structured output to extract and evaluate against an expected value.
Complete override replacement. Omitted credentials and redacted server secrets are preserved when their endpoint URL is unchanged. Send credentials: [] to clear credentials; omit a server container to remove it.
Latency ceilings for voice simulations. Omit to leave unchanged; send an empty array to remove all latency expectations.
Optional folder path for organizing scenarios. Supports up to 3 levels (e.g., “dept/feature/variant”). Set to null to remove from folder.
Response
This is the ISO 8601 date-time string of when the scenario was created.
This is the ISO 8601 date-time string of when the scenario was last updated.
This is the script/instructions for the tester to follow during the simulation.
This is the structured output-based evaluation plan for the simulation. Each item defines a structured output to extract and evaluate against an expected value.
Scenario-level tool call mocks to use during simulations.
Latency ceilings for voice simulations. Each expectation aggregates the target call’s per-turn latencies and fails the simulation (when required) if the aggregated value exceeds its threshold. Skipped for chat simulations and GPT Live targets; on any other voice simulation, a metric that no turn measured fails.
Optional folder path for organizing scenarios. Supports up to 3 levels (e.g., “dept/feature/variant”). Maps to GitOps resource folder structure.