Bulk Delete Traces

Bulk-delete traces matching the same filters as GET .

Strategy: select the matching trace ids first, then DELETE both tables by id. Two queries instead of a join keeps the SQL portable across PG and SQLite and avoids DELETE ... USING syntax that SQLite does not support.

DELETE /admin/api/v1/traces

Bulk Delete Traces

cURL

curl --request DELETE \
  --url https://api.example.com/admin/api/v1/traces

200

{
  "deletedTraces": 123,
  "deletedSpans": 123
}

Query Parameters

started_after · string<date-time> | null

started_before · string<date-time> | null

model · string | null

status · string | null

user_id · string | null

session_id · string | null

name_contains · string | null

Response

200

application/json

Successful Response

Body of DELETE /admin/api/v1/traces (bulk by filter).

The filter shape mirrors :class:StandaloneTraceListFilters (minus limit / cursor); the response counts what was removed.

deletedTraces · integer · required

deletedSpans · integer · required