Get the customer-readable trace for a v2 conversation, nested Session→Turn→node→step
Changed onThe nested tree variant of the session trace (Phase D), paginated by TURN. Same auth (TRACE_READ) + org scoping + terminal-session cache as the flat read. The first page pins the ordered turn roster while every page hydrates current turn content. A window of limit turns is returned with a next_cursor for the next block (None on the last page). If an expired roster changed, the endpoint returns 409 so the client can restart rather than mix traversals. header + session lane ride every page.
Request
- The document declares no server URL.
- AuthAPI key in header x-api-key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Query parameters
Opaque turn-pagination cursor: pass the previous page's next_cursor to load the next block from the same turn roster. Omit for the first page.
Max TURNS per page (the grouped tree paginates by turn, not by raw step).
Response
Successful Response
Changes
- info
added the non-success response with the status
- info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status - info
added the optional property
//////to the response with the status - info
added the optional property
//////to the response with the status
- info
- info
endpoint added
- info