AsyncAPI channel · Lichess · Lichess Streaming API

/api/stream/game/{id}

Stream positions and moves of any ongoing game. A description of the game is sent as the first message; a message is then sent each time a move is played; finally, a description of the game is sent when it finishes and the stream is closed. Ongoing games are delayed by 3 moves to discourage cheating. No more than 8 concurrent streams per IP.

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

Channel address

/api/stream/game/{id}

Parameters

Operations

streamGameMoves
Stream moves of any ongoing game (ND-JSON)

Messages

streamGameDescription
Game description emitted as the first and last message of `/api/stream/game/{id}`.
Content-Type: application/x-ndjson
streamGameMove
Position update emitted on `/api/stream/game/{id}` for each move played (delayed by 3 moves for cheating prevention).
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.