Agent Traces API
Fetch the activity timeline for a Steel browser session as JSON.
Use the Agent Traces API when you want the same activity timeline shown in the dashboard, but as JSON for analysis, replay, or internal tooling.
GET /v1/sessions//agent-traces
Returns the trace timeline for a finished or in-progress session.
Response
| Field | Type | Notes |
|---|---|---|
events | array | Timeline activities in chronological order. |
total | number | Number of activities returned. |
hasMore | boolean | Whether more activity data is available. |
Each activity includes a small common envelope:
| Field | Type | Notes |
|---|---|---|
type | string | Activity type, such as click, input, navigate, scroll, drag, or error. |
timestamp | ISO 8601 string | When the activity happened. |
endTimestamp | ISO 8601 string | Present when the activity spans a range of time. |
page | object | Page context, usually including url. |
target | object | Element context when available. |
Activity-specific details appear when relevant. For example, click activities can include pointer, typing activities can include value, keyboard activities can include keyboard, navigation activities can include navigation, and error activities can include error.
Target Details
When Steel can identify the element involved in an activity, target can include readable labels and useful selectors:
Use target details as hints for review or replay. Some activities, such as navigation or errors, may not include a target.
Filtering by Time
You can limit results to a time range:
| Query param | Notes |
|---|---|
startTime | Include activities at or after this ISO timestamp. |
endTime | Include activities at or before this ISO timestamp. |
Errors
| Status | Meaning |
|---|---|
| 401 | Missing or invalid steel-api-key. |
| 403 | The session belongs to a different organization. |
| 404 | No session with that ID. |
| 429 | Rate limit hit. Retry after the Retry-After header. |
Reach out on the #help channel on Discord under the ⭐ community section.