LCU API alternative
LCU API alternative for League of Legends esports apps.
LCU is useful for local League Client workflows. Cito API is the hosted REST option for server-side LoL esports apps, bots, dashboards, and match centers.
API response preview
League of Legends live match data
T1 vs Gen.G
Live data ready
T1
LCK
2
Gen.G
Game 4
1
Live endpoints
statsAvailable=true/api/v1/lol/liveActive matches and series state
/api/v1/lol/games/{gameId}/statsGame-level player stats
/api/v1/lol/webhooks/eventsPaid-plan update triggers
fetch("https://api.citoapi.com/api/v1/lol/live", {
headers: { "x-api-key": process.env.CITO_API_KEY }
})Live
match state
Stats
game rows
JSON
REST API
Quick recommendation
Is LCU API the right League of Legends API for an esports app?
Use LCU only for allowed local League Client workflows. Use Cito API when you need a hosted League of Legends esports API for a server-side app, Discord bot, dashboard, or match center.
Cito does not depend on the user running League Client. Your backend can request schedules, live matches, teams, players, rosters, game stats, and webhook event metadata from one hosted API.
How to choose
Use this comparison when you need to decide between a local client integration and a hosted API your backend can call.
LCU fit
Local tools that integrate with the League Client under Riot policy constraints.
Cito fit
Hosted server-side products that need LoL esports matches, schedules, teams, players, and stats.
Deployment
Cito runs from your backend. LCU depends on a local client environment.
First request
Use /api/v1/lol/live or /api/v1/lol/schedule/today for server-side LoL app data.
Is LCU API public production infrastructure?
No. It is tied to local League Client workflows and policy constraints.
Why use Cito instead of LCU?
Use Cito when the app must run on your server, power a public website, or serve a Discord bot without a local client.
Does Cito need a Riot production key?
Cito provides its own API access for Cito endpoints. Follow Cito docs and keep the API key server-side.
Can Cito power live alerts?
Yes. Use live endpoints first, then webhooks on paid plans when the product needs event-driven updates.
Full game stats
Build LoL game pages from one detailed API response.
Show teams, objectives, draft, player stat rows, item builds, and key timeline events without stitching together a pile of scrapers.
/api/v1/lol/games/{gameId}/statsUse this for post-game pages, fantasy scoring, wiki updates, Discord recaps, and dashboards.
T1
Win
18
Gen.G
Loss
12
Game 4
T1 wins
34:12 • Patch 15.8
Patch
15.8
Duration
34:12
Winner
T1
Game
4
League
LCK
Stats
Published
Doran
T1
K'Sante
3 / 2 / 8
284
19.4k
Oner
T1
Xin Zhao
5 / 3 / 10
218
16.8k
Faker
T1
Azir
4 / 1 / 11
331
27.2k
Gumayusi
T1
Kai'Sa
6 / 2 / 7
357
30.5k
Keria
T1
Rakan
0 / 4 / 16
42
6.1k
Kiin
Gen.G
Rumble
4 / 5 / 4
301
28.8k
Canyon
Gen.G
Vi
2 / 4 / 7
196
12.3k
Chovy
Gen.G
Orianna
3 / 2 / 6
372
26.9k
Endpoints
Concrete LoL API endpoints developers can build around.
Start with /api/v1/lol/matches/live, then combine live, player, team, match, and webhook endpoints based on the product you are building.
/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/teamsTeam records for directories, dashboards, and wiki pages.
/api/v1/lol/playersPlayer records for profiles, search, and stats pages.
/api/v1/lol/players/{playerId}/statsPlayer stat summaries for profiles and rankings.
/api/v1/lol/games/{gameId}/statsGame-level player stats after publication.
/api/v1/lol/webhooks/eventsSupported LoL webhook events for paid plans.
Use cases
Built for League of Legends apps developers actually launch.
LCU alternative
Use Cito endpoints for the data, then build the dashboard, bot command, profile page, or scoring feature on top.
Hosted LoL apps
Use Cito endpoints for the data, then build the dashboard, bot command, profile page, or scoring feature on top.
Server-side bots
Use Cito endpoints for the data, then build the dashboard, bot command, profile page, or scoring feature on top.
Match centers
Use Cito endpoints for the data, then build the dashboard, bot command, profile page, or scoring feature on top.
Team directories
Use Cito endpoints for the data, then build the dashboard, bot command, profile page, or scoring feature on top.
Live alerts
Use Cito endpoints for the data, then build the dashboard, bot command, profile page, or scoring feature on top.
Do not build a web product on a local client API
LCU is tied to League Client usage and policy constraints. If the product needs to run on your server, use hosted endpoints for schedules, matches, teams, players, and stats.
Use the right API for the job
Use LCU for allowed local client tools. Use Cito when the app is a public esports dashboard, Discord bot, wiki, fantasy product, or backend data pipeline.
Pricing
Start free. Upgrade when your LoL product needs room to grow.
Free testing includes 500 requests/month. Paid plans start at $25/month for higher limits and commercial projects.