How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Lichess Teams API

Access and manage Lichess teams and their members.

Lichess Teams API is one of 23 APIs that Lichess publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Team. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, a JSON-LD context, and 2 JSON Schemas.

This API exposes 14 operations across 14 paths, and defines 31 schemas. It is described by OpenAPI 3.1.0, at version 2.0.144.

Requests are made against 4 base URLs: https://lichess.org, https://lichess.dev, http://localhost:{port}, http://l.org.

14 operations 14 paths 31 schemas 8 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0.144
Base URL
https://lichess.org
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Lichess Teams API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 23 scopes.

  • OAuth2 — Read [the introduction for how to make authenticated requests](description/authentication).

Paths & Operations 14

Across 14 paths, the API surfaces 14 operations — 8 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Teams 14

Access and manage Lichess teams and their members.

GET
/api/team/{teamId}/swiss
Get team swiss tournaments
apiTeamSwiss 5 params → 200
GET
/api/team/{teamId}
Get a single team
teamShow 1 param → 200
GET
/api/team/all
Get popular teams
teamAll 1 param → 200
GET
/api/team/of/{username}
Teams of a player
teamOfUsername 1 param → 200
GET
/api/team/search
Search teams
teamSearch 2 params → 200
GET
/api/team/{teamId}/users
Get members of a team
teamIdUsers 2 params → 200
GET
/api/team/{teamId}/arena
Get team Arena tournaments
apiTeamArena 5 params → 200
POST
/team/{teamId}/join
Join a team
teamIdJoin 1 param body → 200
POST
/team/{teamId}/quit
Leave a team
teamIdQuit 1 param → 200
GET
/api/team/{teamId}/requests
Get join requests
teamRequests 2 params → 200
POST
/api/team/{teamId}/request/{userId}/accept
Accept join request
teamRequestAccept 2 params → 200
POST
/api/team/{teamId}/request/{userId}/decline
Decline join request
teamRequestDecline 2 params → 200
POST
/api/team/{teamId}/kick/{userId}
Kick a user from your team
teamIdKickUserId 2 params → 200
POST
/team/{teamId}/pm-all
Message all members
teamIdPmAll 1 param body → 200400

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are ArenaTournament (27 properties), Perfs (18 properties), SwissTournament (15 properties), User (14 properties). Each schema is shown below with its type and property counts.

PuzzleModePerf
object
2 properties 2 required
PatronColor
integer
Players can choose a color for their Patron wings. See [here for the color mappings](https://github.com/lichess-org/lila/blob/master/ui/lib/css/abstract/patron…
Verdicts
object
2 properties 2 required
Variant
object
3 properties 2 required
ArenaPerf
object
4 properties 3 required
ArenaStatus
integer
10: created, 20: started, 30: finished
PlayTime
object
3 properties 2 required
Patron
boolean
Use patronColor value instead to determine if player is a patron.
ArenaStatusName
string
The current state of the arena tournament
VariantKey
string
TeamRequest
object
4 properties 3 required
Ok
object
1 property 1 required
PerfType
string
Team
object
10 properties 2 required
SwissTournament
object
15 properties 13 required
Profile
object
11 properties
Verdict
object
2 properties 2 required
Clock
object
2 properties 2 required
Flair
string
See [available flair list and images](https://github.com/lichess-org/lila/tree/master/public/flair)
Perf
object
6 properties 4 required
Error
object
1 property 1 required
User
object
14 properties 2 required
Perfs
object
18 properties
ArenaPosition
LightUser
object
6 properties 2 required
TeamRequestWithUser
object
2 properties 2 required
TeamPaginatorJson
object
7 properties 7 required
Title
string
only appears if the user is a titled player or a bot user
ArenaTournament
object
27 properties 13 required
ArenaRatingObj
object
2 properties 1 required
SwissStatus
string
The current state of the swiss tournament

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lichess-teams-api-openapi.yml Raw ↑

Other APIs Lichess publishes across the network.

Lichess Account API
Lichess Analysis API
Lichess Board API
Lichess Bot API
Lichess Broadcasts API
Lichess Bulk pairings API
Lichess Challenges API
Lichess External engine API
Lichess FIDE API
Lichess Games API
Lichess Messaging API
Lichess OAuth API
Where this information came from

This is an independent, third-party profile of Lichess Teams API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.