LedgeKitDocs
API referenceHTTP API
Developer documentation

List traces

Query trace summaries within a read key's app and environment.

curl --fail-with-body --get https://api.ledgekit.com/v1/traces \
  -H "Authorization: Bearer $LEDGE_READ_KEY" \
  --data-urlencode 'name=summarize-text' \
  --data-urlencode 'limit=20'

The response is an object containing appId, mode, traces, and nextCursor. Each summary includes definition name/version, display status, timing, and its agent definitions. It does not contain full prompts or output; fetch trace detail for the envelope.

Filters and pagination

limit defaults to 50 and accepts 1–100. version requires name; agentVersion requires agent. Versions must be positive integers. from and to are timestamp bounds on receipt time, with from no later than to.

Results are ordered by receipt time descending, then trace ID descending. If nextCursor is not null, send it as cursor with the same read key and filters. Treat the cursor as opaque. Start a new query after changing filters or rotating keys. The optional appId filter cannot expand key access.

Unknown or repeated query parameters, malformed cursors, and incompatible filters return 400 invalid_query. URL-encode the partial success status when using it as a filter.

Loading API schema…

On this page