AsyncAPI channel · Lichess · Lichess Streaming API

/api/stream/event

Stream events reaching a Lichess user in real time (Board + Bot APIs). An empty line is sent every 7 seconds for keep-alive purposes. When the stream opens, all current challenges and games are sent. Only one global event stream can be active at a time per access token.

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

Channel address

/api/stream/event

Operations

streamIncomingEvents
Stream incoming Board/Bot events (ND-JSON)

Messages

gameStart
Start of a game (sent on the incoming events stream).
Content-Type: application/x-ndjson
gameFinish
Completion of a game (sent on the incoming events stream).
Content-Type: application/x-ndjson
challenge
A player sends you a challenge, or you challenge someone.
Content-Type: application/x-ndjson
challengeCanceled
A player cancels their challenge to you.
Content-Type: application/x-ndjson
challengeDeclined
The opponent declines your challenge.
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.