Event Stream

Allternit exposes two real-time channels for observing beta session events:

Server-Sent Events (SSE) at GET /api/v1/beta/sessions/:id/events
WebSocket at GET /api/v1/beta/sessions/:id/events/ws

GET /api/v1/beta/sessions/:id/events/list returns the same events as one JSON page. Both streams emit the same underlying events. Use SSE for simple one-way observation. Use WebSockets when you need bidirectional communication, such as closing the connection from the client side or sending an interrupt through a separate HTTP call.

Authentication

Both endpoints require a valid bearer token. See Authentication.

Event types

Event	Description
`session_created`	The session was created.
`budget_updated`	The session budget was created or changed.
`thinking_delta`	A reasoning delta appended by a caller.
`content_block_delta`	A content delta appended by a caller.
`tool_calls`	One or more tool calls were appended.
`refusal`	A refusal event was appended.
`context_warning`	Projected usage crossed 80% of `context_window`.
`budget_exceeded`	A hard budget limit was exceeded.
`user_interrupt`	A user interrupt was posted.
`context_summary`	Events were summarized during context editing.
`session_archived`	The session was archived.

Only thinking_delta, content_block_delta, tool_calls, and refusal may be appended directly by callers. All other event types are emitted by the platform.

SSE example

curl -N -H "Authorization: Bearer $ALLTERNIT_API_KEY" \
  https://api.allternit.com/api/v1/beta/sessions/sess_123/events

Add ?after=<sequence> to resume from a known sequence number.

Stream format

event: tool_calls
id: 7
data: {"calls":[{"name":"bash","input":{"command":"cargo test"}}]}

WebSocket example

websocat -H "Authorization: Bearer $ALLTERNIT_API_KEY" \
  wss://api.allternit.com/api/v1/beta/sessions/sess_123/events/ws

Each message is a JSON object:

{
  "sequence": 7,
  "type": "tool_calls",
  "data": { "calls": [{ "name": "bash", "input": { "command": "cargo test" } }] }
}

Notification feed

GET /api/v1/events/stream (allternit-api) is one SSE feed across all of the caller’s bots. Allternit Desktop uses it to raise native notifications while the window is hidden. It sends only events worth interrupting someone for, as event: notify with id: set to a ledger cursor:

{
  "kind": "channel_message",
  "eventType": "channel.message.received",
  "botId": "bot-1",
  "botName": "Ledger",
  "threadId": "th-1",
  "threadTitle": "Sam on Telegram",
  "text": "first 240 characters",
  "from": null,
  "channel": "telegram",
  "occurredAt": "2026-10-03T10:00:00Z"
}

kind is channel_message (a message reached a bot through a channel), missed_call (a call.ended marked missed, answered: false or reason missed/no_answer) needs_you (thread.needs_user, which includes an email held for approval) or inbox_changed (the owner dismissed, snoozed or approved an item in the Needs you inbox; clients refresh the list and never notify). It reads bot_events, so only the caller’s own bots appear and nothing is replayed on a fresh connection. Reconnect with Last-Event-ID (or ?after=) to resume. A keep-alive comment is sent every 20 seconds. The same classification decides which ledger rows go to the cloud event backbone. See Runtime events forwarder.

Platform API

Legal

Overview

Agency API (Preview)

LLM Gateway

Agents & Runtime

Work Queue & Deployments

Files, Webhooks & Sandbox

Tools & Connectors

Collaboration & Workflows

Infrastructure & Platform

Canvases

Onboarding

A Labs

Playground

Users & Profiles

Event Stream

Event Stream

Authentication

Event types

SSE example

Stream format

WebSocket example

Notification feed

​Event Stream

​Authentication

​Event types

​SSE example

​Stream format

​WebSocket example

​Notification feed

​Related pages

Event Stream

Authentication

Event types

SSE example

Stream format

WebSocket example

Notification feed

Related pages