Connect

Upgrades the HTTP connection to a WebSocket for receiving real-time live blog events.

Authentication uses the short-lived JWT obtained from POST /v1/token, passed as the token query parameter (defined by the shortLivedToken security scheme).

If a timestamp is provided, the server replays all matching Redis stream messages from that point before emitting live events, enabling seamless reconnection after a drop.


Server → Client message topics:

TopicDescriptionPayload
pingKeep-alive ping; client must reply with pongnone
reconnectServer is shutting down gracefully; client should reconnectnone
activityViewer count update{ "viewers": <integer|null> }
blog-updateLive blog metadata was updatedevent payload from Redis stream
blog-deleteLive blog was deletedevent payload from Redis stream
post-createA post was createdevent payload from Redis stream
post-updateA post was updatedevent payload from Redis stream
post-deleteA post was deletedevent payload from Redis stream

Client → Server message topics:

TopicDescription
pongResponse to server ping. Prevents idle timeout.

All WebSocket messages use the shape { "topic": "<topic>", "payload": <object> }. Unknown client topics cause the server to close the connection.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
date-time

RFC3339 timestamp. When provided, the server replays all historical stream messages since this point (minus a configurable offset) before switching to live events. Use this to catch up on missed events after a reconnection.

Responses
101

WebSocket connection established. The HTTP connection is upgraded to the WebSocket protocol.

Language
Credentials
Query
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json