Documentation Index
Fetch the complete documentation index at: https://mintlify.com/everruns/everruns/llms.txt
Use this file to discover all available pages before exploring further.
GET /v1/sessions//events
List events for a session as JSON. This is an alternative to the SSE endpoint for non-streaming use cases.Path Parameters
The unique identifier of the session
Query Parameters
Return events after this event ID. Used for pagination and incremental fetching.
Positive filter: Only return events matching these types. Empty = all types.Repeated key format:
?types=turn.started&types=turn.completedMaximum 25 values. Must be known event types.Negative filter: Exclude events matching these types. Applied after
types filter.Repeated key format: ?exclude=output.message.delta&exclude=reason.thinking.deltaMaximum 25 values. Must be known event types.Filter Semantics
When bothtypes and exclude are provided:
typesnarrows to matching event types firstexcluderemoves from that set
Response
Returns a non-paginated list of all events matching the filters.Array of event objects
Event identifier (UUID v7)
Event type in dot notation (e.g.,
input.message, turn.started)ISO 8601 timestamp with millisecond precision
Session this event belongs to
Correlation context for tracing
Event-specific payload
Optional arbitrary metadata
Tags for filtering and categorization
Total number of events returned
Example Request
Example with Filters
Example Response
Event Schema
Every event conforms to the standard event schema. See Event Streaming for detailed field descriptions.Common Event Types
Input Events
input.message- User message submitted
Output Events
output.message.started- Agent starts generating responseoutput.message.delta- Streaming text update (batched ~100ms)output.message.completed- Agent response completed
Turn Events
turn.started- Turn execution startedturn.completed- Turn completed successfullyturn.failed- Turn failedturn.cancelled- Turn cancelled by user
Session Events
session.started- Session execution startedsession.activated- Session became active (turn started)session.idled- Session became idle (turn completed, includes token usage)
Atom Events
reason.started/reason.completed- LLM reasoning phaseact.started/act.completed- Tool execution batchtool.started/tool.completed- Individual tool execution
LLM Events
llm.generation- Full LLM API call with messages and response
Extended Thinking Events
reason.thinking.started- Extended thinking startedreason.thinking.delta- Streaming reasoning contentreason.thinking.completed- Extended thinking completed
Use Cases
Polling for New Events
Usesince_id to incrementally fetch new events:
Filtering Verbose Events
Exclude high-frequency streaming events to reduce payload size:Monitoring Turn Lifecycle
Get only turn lifecycle events for monitoring:Error Responses
Error message
HTTP status code
Common Errors
- 400 Bad Request: Invalid filter parameters (unknown event type, too many values)
- 404 Not Found: Session does not exist
- 500 Internal Server Error: Server error during retrieval