Connecting to SSE Endpoints

Quick Start

Connecting to an SSE endpoint is straightforward:

1

Create an SSE Tab

Click the + button in the tab bar and select "SSE". You'll see the SSE interface with the connection bar at the top.

2

Enter the URL

Type or paste the SSE endpoint URL in the URL field. Example: https://api.example.com/events

3

Click Connect

Click the Connect button or press Enter while in the URL field.

Watch Events Arrive

Once connected, events will appear in the Events panel as they arrive from the server.

Using Environment Variables

You can use environment variables in the URL using the {{variable}} syntax:

{{baseUrl}}/events/stream

https://api.example.com/events/stream

This allows you to easily switch between different servers (development, staging, production) by changing the environment without modifying the URL.

Authentication

Many SSE endpoints require authentication. Configure auth in the Settings panel on the left:

BearerToken Authentication

For JWT tokens or API tokens. Sends as Authorization: Bearer <token>

Authorization: Bearer eyJhbGciOiJIUzI1NiIs...

Tip: Use {{token}}to store the token in environment variables for easy switching.

BasicUsername & Password

Classic HTTP Basic Auth. Credentials are Base64-encoded and sent in the header.

Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=

Enter username and password in the Auth section. Tigrister handles the encoding automatically.

API KeyCustom Header Authentication

Send the API key in a custom header (e.g., X-API-Key) or as a query parameter.

Header:
X-API-Key: sk-abc123...
Query:
?api_key=sk-abc123...
NoneNo Authentication

For public SSE endpoints that don't require authentication. This is the default.

Reconnection & Resuming

SSE has built-in support for resuming streams after disconnection. Use the Last-Event-ID field in the Settings panel:

How It Works
1

Each event from the server can include an id field.

2

If connection is lost, note the last event ID you received (visible in the event list).

3

Enter that ID in the "Last-Event-ID" field before reconnecting.

4

On reconnect, Tigrister sends Last-Event-ID: <id> header.

Server resumes from that point (if it supports this feature).

Server Support Required

The server must implement event ID tracking and resumption logic. Not all SSE servers support this feature. Check your server's documentation.

Connection States

The connection bar shows the current state with color coding:

IdleNot connected. Ready to connect.
ConnectingEstablishing connection to the server.
ConnectedConnected and receiving events.
ReconnectingConnection lost, attempting to reconnect.
DisconnectedCleanly disconnected by user or server.
ErrorConnection failed. Check URL and auth settings.

Disconnecting

To disconnect from an SSE stream:

Click the Disconnect button in the connection bar. The connection will be cleanly closed.

Events received so far remain in the Events panel. Clear them manually with the trash icon if needed, or they'll be cleared when you close the tab.

URL Editing

The URL field is disabled while connected to prevent accidental changes. Disconnect first if you need to modify the URL.

Testing Tips

Use Test Endpoints

Many public SSE endpoints exist for testing. Search for "SSE test server" to find endpoints that send periodic events.

Check the Raw View

When debugging, expand an event and switch to the "Raw" tab to see the exact SSE protocol format received from the server.

Monitor Connection Status

Keep an eye on the connection info footer (Status and ID) to verify successful connections and track connection identity.

Test Reconnection

Note an event ID from the list, disconnect, enter that ID in Last-Event-ID, then reconnect to verify your server's reconnection support.