conversations

Get the customer-readable trace for a v2 conversation, nested Session→Turn→node→step

Changed on

The 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.

get/v1/conversations/{conversation_id}/trace/grouped

Request

Path parameters

conversation_idstring uuid required

Query parameters

turn_idstring uuid nullable
cursorstring nullable

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.

limitinteger

Max TURNS per page (the grouped tree paginates by turn, not by raw step).

category'product' | 'engineering' | 'all'

Response

Successful Response

next_cursorstring nullable

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

      endpoint added