Skip to main content
GET
List traces
Requires the IAM action telemetry:ReadTraces. See TELEMETRY permissions for the full list, what each one covers, and an example policy.

Authorizations

Authorization
string
header
required

An OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. This is the recommended way to authenticate.

Get one by exchanging a service account's access key pair at POST /v1/oauth/token with grant_type=client_credentials. It is the standard client-credentials grant, so any OAuth-aware library will obtain and refresh it for you.

Tokens last an hour by default. The same access key pair is separately your AWS SigV4 credential for the S3-compatible object endpoint, which speaks nothing else.

Query Parameters

from
string<date-time>
required

Lower bound on span start_time (inclusive)

Example:

"2026-01-15T00:00:00Z"

to
string<date-time>
required

Upper bound on span start_time (exclusive); must be after from and within 31d

Example:

"2026-01-16T00:00:00Z"

service
string

Filter by service.name

Example:

"api-gateway"

operation
string

Filter by span name (operation)

Example:

"GET /api/users"

status_code
enum<string>

Filter by status code

Available options:
UNSET,
OK,
ERROR
Example:

"ERROR"

min_duration_ms
number<double>

Filter to traces whose end-to-end duration is at least this many ms

Required range: x >= 0
Example:

100

limit
integer
default:50

Maximum number of items to return. A value above the maximum is clamped to it rather than rejected, so a page shorter than the one you asked for is normal — page until meta.has_more is false, not until a page looks short.

Required range: 1 <= x <= 100
marker
string

Opaque pagination cursor. Echo back the meta.marker value from the previous page to fetch the next one; do not construct or parse it. The token's internal form varies by endpoint (a resource ID, a timestamp, …) and is not guaranteed stable across releases.

Response

Page of trace summaries

traces
object[]
required
meta
object
required