AsyncAPI channel · Lichess
· Lichess Streaming API
/api/games/user/{username}
Export all games of any user. The stream is sorted by reverse chronological
order. Throttled to 20 games/sec for anonymous requests, 30/sec for OAuth, and
60/sec when downloading your own games. Returns ND-JSON when the request
Accept header is `application/x-ndjson`, or PGN when `application/x-chess-pgn`.
username — The Lichess username whose games to export.
Operations
subscribe
streamUserGames
Export user games (ND-JSON or PGN)
Messages
userGameJson
A single game export entry from `/api/games/user/{username}` (ND-JSON).
Content-Type: application/x-ndjson
userGamePgn
A single PGN export entry from `/api/games/user/{username}` (PGN).
Content-Type: application/x-chess-pgn
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.