LoL team API

Team profiles, logos, rosters, matches, and stats for LoL apps.

Fetch the team page data developers need: name, logo, region, leagues, roster, recent matches, objective rates, achievements, and earnings where tracked.

Team metadata
Org logos
League membership
Team stats

API response preview

Team profile data for org pages and match centers

JSON

Useful endpoints

/api/v1/lol/teams/{slug}

Team profile

/api/v1/lol/teams/{slug}/matches

Team match history

/api/v1/lol/teams/{slug}/objectives

Objective rates

Run the request

X-API-Key
curl "https://api.citoapi.com/api/v1/lol/teams/{slug}" \
  -H "X-API-Key: $CITO_API_KEY"
{
  "slug": "t1",
  "name": "T1",
  "shortName": "T1",
  "region": "KOREA",
  "logoUrl": "https://...",
  "rosterCount": 6,
  "leagues": [{ "slug": "lck", "name": "LCK" }]
}

Primary endpoint: /api/v1/lol/teams/{slug}

Fetch the team page data developers need: name, logo, region, leagues, roster, recent matches, objective rates, achievements, and earnings where tracked.

Team metadataOrg logosLeague membershipTeam stats

Endpoint chain

Start with /api/v1/lol/teams/{slug}, then add the supporting rows your screen needs.

The first request should answer the user's main question. Add live state, roster rows, match stats, transfer history, or earnings only when the UI needs that detail.

GET
/api/v1/lol/teams/{slug}

Team profile data for org pages and match centers.

Team profile

/api/v1/lol/teams/{slug}

Use this first when the page needs team profile data for org pages and match centers.

Team match history

/api/v1/lol/teams/{slug}/matches

Team match history fills in the detail around the primary response.

Objective rates

/api/v1/lol/teams/{slug}/objectives

Objective rates fills in the detail around the primary response.

Returned data

Fetch the team page data developers need: name, logo, region, leagues, roster, recent matches, objective rates, achievements, and earnings where tracked.

Best first request

Call /api/v1/lol/teams/{slug} from your backend and cache the response based on how often that screen changes.

Common fallback

If live data is empty, show today's schedule, upcoming matches, recent results, or the last known team/player rows.

API key handling

Keep the API key on your server. Send your frontend only the fields it needs to render the page.

Data fit

Use this API for pro matches, teams, players, rosters, stats, and esports history.

If you need Riot ID, PUUID, ranked ladder, champion mastery, or account-linked match history, use Riot's APIs. If you need a pro esports app, use Cito's LoL endpoints.

Pro Esports API

Built for match centers, fantasy products, scouting tools, wikis, dashboards, team pages, player pages, and live bots.

Live matches and schedules
Pick/ban and game stats where published
Tournament brackets and standings
Player earnings and org history
Transfer tracking
Roster history

Ranked and Ladder Workflows

Use Riot APIs for direct Riot ID, PUUID, summoner, match history, ranked ladder, champion mastery, and account-linked workflows. Cito only references public pro-player account context where source data allows it.

Resources

Docs, examples, and machine-readable endpoint files.

Open the docs when you want examples. Import Postman when you want to test. Use the endpoint manifest when an AI coding tool needs exact paths.

FeatureCito APIRiot APIPandaScore
PriceFree testing, Starter $25/mo, Builder $50/moFree, rate limited; production approval variesUsually sales/custom pricing
Ranked account dataNot the primary product; use Riot for direct account workflowsYesNot the core LoL ranked source
Pro esports liveYesFragmented across official surfacesYes
Player earningsYesNoProvider-dependent
Org/transfer historyYesCurrent GCD affiliation/contract data, not full historyProvider-dependent
Unified REST APIYesMultiple products and routing modelsYes
Instant signupYesDeveloper key yes; production can require approvalOften sales-led

Riot's API is free but fragmented. PandaScore is enterprise-only. Cito is the only self-serve option with earnings and org history.

Endpoints

Endpoint paths for this workflow.

Start with /api/v1/lol/teams/{slug}. Add supporting endpoints only when your page needs more context.

GET
/api/v1/lol/players/{playerId}/earnings

Career prize pool earnings with tournament-by-tournament rows.

GET
/api/v1/lol/players/{playerId}/earnings/summary

Player earnings totals, event counts, placements, and tracked history.

GET
/api/v1/lol/players/{playerId}/teams

Team history for org changes, roles, and date ranges.

GET
/api/v1/lol/teams/{slug}/roster/history

Historical rosters with roster membership periods.

GET
/api/v1/lol/transfers

Recent transfer activity across tracked LoL teams and players.

GET
/api/v1/lol/teams/{slug}/earnings

Organization-level earnings and tournament results where tracked.

GET
/api/v1/lol/live

Active League of Legends esports matches and live state.

GET
/api/v1/lol/schedule/today

Today's LoL esports schedule for match-day apps.

GET
/api/v1/lol/games/{gameId}/stats

Game-level player stats after source publication.

GET
/api/v1/lol/webhooks/events

Supported LoL webhook events for paid plans.

Use cases

Built for League of Legends apps developers actually launch.

Team profile pages

Show logo, region, leagues, roster, recent matches, objective rates, and achievements.

Org directories

Build searchable directories with team names, short names, logos, regions, and active status.

Fantasy team pages

Show recent form, upcoming schedule, roster context, and objective rates for each team.

Scouting dashboards

Compare teams by match history, objective control, champion pool, and roster movement.

Wiki pages

Populate team, player, roster, match, tournament, and earnings pages from structured endpoints.

Match center team cards

Show each side's logo, roster, league, recent matches, and current series context.

One team slug, one profile

Use the team slug to load logo, region, short name, current roster, league context, recent matches, objective rates, earnings, and achievements.

Aliases resolve cleanly

Common org aliases resolve to the current team record, so old slugs do not create duplicate team pages in your app.