Server-Sent Events (SSE)
Real-time streaming from server to client, with a purpose-built interface.
What is SSE?
Server-Sent Events (SSE) is a standard for real-time, one-way communication from server to client over HTTP. Unlike WebSockets which are bidirectional, SSE is specifically designed for scenarios where the server needs to push updates to the client.
Why SSE?
- • Simple - Works over standard HTTP, no special protocol
- • Auto-reconnect - Built-in reconnection with Last-Event-ID
- • Firewall-friendly - Uses regular HTTP/HTTPS connections
- • Event-driven - Native event types and IDs
When to Use SSE
Choosing the right protocol depends on your use case:
| Protocol | Direction | Best For |
|---|---|---|
| SSE | Server → Client | Live feeds, notifications, logs, AI streaming responses |
| WebSocket | Bidirectional | Chat, gaming, collaborative editing |
| HTTP | Request → Response | REST APIs, CRUD operations, one-time requests |
Common SSE Use Cases
- • AI/LLM Streaming - ChatGPT, Claude, and other LLMs stream responses via SSE
- • Live Dashboards - Stock prices, metrics, monitoring data
- • Notifications - Push notifications, alerts, system events
- • Log Streaming - Real-time log tailing, CI/CD build output
How SSE Works
SSE is surprisingly simple - it's just a long-lived HTTP response with a special content type:
Tigrister
SSE Endpoint
Client Opens Connection
Sends a regular HTTP GET request with Accept: text/event-stream header.
Server Keeps Connection Open
Responds with Content-Type: text/event-stream and keeps the connection open.
Server Sends Events
Whenever there's new data, server writes it to the response stream as text-based events.
Auto-Reconnect on Disconnect
If the connection drops, the client automatically reconnects and can resume from the last event ID.
Tigrister's SSE Support
Tigrister provides a dedicated SSE testing environment with:
Real-time Event Display
Events appear instantly as they arrive, with automatic JSON formatting and syntax highlighting.
Authentication Support
Full auth support including Bearer tokens, Basic auth, and API keys - same as HTTP requests.
Reconnection Support
Resume from any event using Last-Event-ID. The server continues from where you left off.
Raw Protocol View
View events in both formatted (Content) and raw SSE protocol format for debugging.