Get a test scenario
Read one scenario's full payload, name, type, folder, tags, the per-type caller script (conditions / instructions / callerUtterances), the expected-outcome judge prompt, attached metricIds, persona, the linked test profile with its variables, caller tool toggles, language, connectionMode, toolMode, agentSpeaksFirst, callerModel, its assertions, workflowChecks, callSetup and line-condition environment, and its latest run status. Use this before update_scenario so you patch from the current state rather than guessing, list_scenarios only returns summaries.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Path Parameters
Workspace slug (GET /me lists yours).
Agent slug within the workspace.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://example.com/workspaces/string/agents/string/tests/string"{
"scenario": {
"id": "string",
"name": "string",
"property1": null,
"property2": null
},
"property1": null,
"property2": null
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}Delete a test scenario DELETE
Permanently delete one scenario (scenarioId) or many (scenarioIds) from the agent's test library. The scenarios' run history is deleted with them (FK cascade), this cannot be undone, so confirm with the operator before bulk deletes. Resolve ids with list_scenarios first. Returns the deleted count; an id that isn't on this agent reports not-found rather than silently succeeding.
List test scenarios GET
List the agent's test-harness scenarios (the simulated callers the eval engine plays) with each one's id, name, scenarioType (conditional / instruction / scripted), folder, tags, and latest-run status. Call this FIRST to resolve a scenario id before update_scenario, and before create_scenario so you don't duplicate one that already exists. Optionally filter by folder. This reads the test harness, it does not change the agent.