List the traces this person created

The stable directory user id — the same id GET /users/{user_id} takes, and the one trace ownership is keyed on.

Window start, inclusive (unix epoch seconds, UTC).

Window end, exclusive (unix epoch seconds, UTC).

Page size.

Opaque resume token from a prior page's page.next_cursor. Bound to the caller, the access policy and the scope that produced it, so it cannot be replayed across a policy change.

Trace ordering. Defaults to started_at_desc — newest first.

This param takes the trace store's own enum spelling, not the registry's -field grammar. started_at_desc / started_at_asc, and a leading - means nothing here. Stated because the two dialects sit side by side on one surface, and a sort param that documents neither its accepted values nor its default leaves a client no way to discover either but by trying.

Narrow the list to these traces: how a caller checks which traces in a batch exist. Comma-separated, 1–100 distinct trace ids, each 32 lowercase hex characters and not all zeros. Requires both start_time_unix_seconds and end_time_unix_seconds, within the usual 365-day limit, and limit then defaults to 100. A trace recorded in several workspaces is one item per workspace, so keep following page.next_cursor until it is absent, sending the same trace_ids each time. An id absent from every page is not visible to you in that window; an error response never means an id is absent.