---
title: "Read Scenario Transcript"
method: GET
path: "/admin/simulations/{engagement_id}/scenario-transcript"
tags: ["admin", "simulations"]
---

# Read Scenario Transcript

`GET /admin/simulations/{engagement_id}/scenario-transcript`

## Request

- Base URL: `https://api-docs.upsmith.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api-docs.upsmith.com/admin/simulations/{engagement_id}/scenario-transcript`
- Auth: one of:
  - API key in header `x-api-key`
  - HTTP bearer

Backend-agnostic, role-labeled scenario transcript, oldest first.

Resolves the run's backend from its scenario meta, so it works for a customer
run (INTERACTION events) and an Ask Jenny run (LLM_RESPONSE events) alike —
unlike ``/messages``, which only reads INTERACTION events and is empty for Jenny.

``include_actions`` interleaves the agent's tool calls (ACTION events, which both
backends persist to ``event_action``) with the messages by time — each carrying
the resolved tool name — so the transcript shows what the agent did between turns.

## Path parameters

- `engagement_id` string, required

## Query parameters

- `include_actions` boolean

## Headers

- `organization-id` string, nullable
- `timezone` string
- `x-user-id` string, nullable
- `x-actor-email` string, nullable
- `x-request-source` string, nullable
- `x-operation-id` string, nullable
- `x-commit-message` string, nullable
- `x-confirmation-id` string, nullable
- `x-chat-id` string, nullable

## Response `200`

Successful Response

- ScenarioTranscriptLine[]
  - `role` string, required
  - `content` string
  - `tool_call` ScenarioToolCall
    - `tool` string, required
    - `input` string, required
    - `output` string, required
    - `success` boolean, nullable

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/upsmith/apis/upsmith-api.md) - [All operations](https://skmtc.dev/upsmith/apis/upsmith-api/llms.txt) - [OpenAPI document](https://skmtc.dev/upsmith/apis/upsmith-api/revisions/cce8b07a5787?raw)