AsyncAPI channel · Lichess · Lichess Streaming API

/api/stream/games/{streamId}

Create a stream of games from an arbitrary `streamId` and a list of game IDs. The stream first emits the games that already exist, then emits an event each time a listed game is started or finished. While the stream is open, new game IDs can be added via `POST /api/stream/games/{streamId}/add`.

Open source AsyncAPI → All Lichess channels Lichess provider profile
Provider: Lichess AsyncAPI: v2.6.0 Spec: Lichess Streaming API Operations: 1 Messages: 1

Channel address

/api/stream/games/{streamId}

Parameters

Operations

streamGamesByIds
Stream games by IDs (ND-JSON)

Messages

gameStreamGame
A game record emitted on `/api/stream/games-by-users` and `/api/stream/games/{streamId}`. Emitted when a game starts or finishes (and for already-running games at stream open when requested).
Content-Type: application/x-ndjson

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.