LoL live score API
Live LoL scores, series state, and current match status.
Show who is playing, what the score is, which game is live, and when the next match starts without scraping LoL Esports pages.
API response preview
Live score rows for scoreboards and alerts
Useful endpoints
/api/v1/lol/liveActive matches
/api/v1/lol/matches/liveLive match alias
/api/v1/lol/schedule/todayFallback when nothing is live
Run the request
X-API-Keycurl "https://api.citoapi.com/api/v1/lol/live" \ -H "X-API-Key: $CITO_API_KEY"
{
"count": 1,
"matches": [
{
"matchId": "lec-2026-g2-fnc",
"state": "inProgress",
"score": { "g2-esports": 1, "fnatic": 0 },
"currentGame": 2
}
]
}Primary endpoint: /api/v1/lol/live
Show who is playing, what the score is, which game is live, and when the next match starts without scraping LoL Esports pages.
Endpoint chain
Start with /api/v1/lol/live, 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.
/api/v1/lol/liveLive score rows for scoreboards and alerts.
Active matches
/api/v1/lol/liveUse this first when the page needs live score rows for scoreboards and alerts.
Live match alias
/api/v1/lol/matches/liveLive match alias fills in the detail around the primary response.
Fallback when nothing is live
/api/v1/lol/schedule/todayFallback when nothing is live fills in the detail around the primary response.
Returned data
Show who is playing, what the score is, which game is live, and when the next match starts without scraping LoL Esports pages.
Best first request
Call /api/v1/lol/live 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.
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.
| Feature | Cito API | Riot API | PandaScore |
|---|---|---|---|
| Price | Free testing, Starter $25/mo, Builder $50/mo | Free, rate limited; production approval varies | Usually sales/custom pricing |
| Ranked account data | Not the primary product; use Riot for direct account workflows | Yes | Not the core LoL ranked source |
| Pro esports live | Yes | Fragmented across official surfaces | Yes |
| Player earnings | Yes | No | Provider-dependent |
| Org/transfer history | Yes | Current GCD affiliation/contract data, not full history | Provider-dependent |
| Unified REST API | Yes | Multiple products and routing models | Yes |
| Instant signup | Yes | Developer key yes; production can require approval | Often 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/live. Add supporting endpoints only when your page needs more context.
/api/v1/lol/players/{playerId}/earningsCareer prize pool earnings with tournament-by-tournament rows.
/api/v1/lol/players/{playerId}/earnings/summaryPlayer earnings totals, event counts, placements, and tracked history.
/api/v1/lol/players/{playerId}/teamsTeam history for org changes, roles, and date ranges.
/api/v1/lol/teams/{slug}/roster/historyHistorical rosters with roster membership periods.
/api/v1/lol/transfersRecent transfer activity across tracked LoL teams and players.
/api/v1/lol/teams/{slug}/earningsOrganization-level earnings and tournament results where tracked.
/api/v1/lol/liveActive League of Legends esports matches and live state.
/api/v1/lol/schedule/todayToday's LoL esports schedule for match-day apps.
/api/v1/lol/games/{gameId}/statsGame-level player stats after source publication.
/api/v1/lol/webhooks/eventsSupported LoL webhook events for paid plans.
Use cases
Built for League of Legends apps developers actually launch.
Live scoreboards
Show active matches, current series score, team names, league, and live state.
Discord live commands
Return the current score and next match from a simple slash command.
Match center headers
Power the top of a match page with teams, score, status, start time, and league.
Overlays
Feed live score and match state into lightweight stream or watch-party overlays.
Fantasy live states
Show whether a slate is waiting, live, completed, or ready for stat refresh.
Alert systems
Trigger alerts when a match moves from scheduled to live or completed.
Live score is narrower than live stats
Many products only need the scoreboard layer first: who is playing, whether the series is live, current score, league, tournament, and start time.
Upgrade into stats when ready
Pair live score endpoints with game stats endpoints when the product needs gold graphs, objective rows, and player-level detail.
Pricing
Start free. Upgrade when your LoL product needs room to grow.
Free testing includes 500 requests/month. Starter handles early products at $25/month. Builder is the $50/month tier for earnings, org history, transfers, webhooks, and higher-volume LoL apps.