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.

Get Free API Key Start LoL for $10 View LoL Docs

Hosted server-side API

No local client dependency

Esports data endpoints

Production app friendly

Most Likely Picks

14G LIVE

Role14-Game TrendPick Chance

Azir

MID

78%

Kalista

BOT

71%

Nautilus

SUP

64%

Rell

SUP

57%

Lee Sin

JNG

50%

Primary endpoint: /api/v1/lol/matches/live

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.

Hosted server-side APINo local client dependencyEsports data endpointsProduction app friendly

Live webhooks

Push LoL gold swings, objectives, kills, towers, and match state into your product.

Riot workflows are strongest after official data is published. Cito is built for product teams that need near-live monitoring during active coverage, then clean post-game reconciliation when final data lands.

Seconds to tens of seconds during active coverage

Unique event IDs for dedupe

Signed delivery headers

Retry attempts with delivery metadata

Start LoL One Game Starter Compare Plans

Example payload

Gold swing webhook

signed

POST /your-webhook
X-Cito-Event: lol.live.gold_swing
X-Cito-Event-Id: 1c11131a-2d74-4b06-b4be-ec873861854b
X-Cito-Delivery-Attempt: 1
X-Cito-Signature: sha256...

{
  "event": "lol.live.gold_swing",
  "id": "1c11131a-2d74-4b06-b4be-ec873861854b",
  "data": {
    "league": "LCS",
    "gameTime": 1716,
    "source": "vision",
    "previousGoldDiff": -1900,
    "goldDiff": -3300,
    "swing": -1400,
    "leadingSide": "red"
  }
}

lol.live.state

Periodic live state snapshot with game time, gold, kills, towers, dragons, Barons, and team IDs.

lol.live.gold_swing

Emitted when the gold lead changes materially or flips side.

lol.live.objective

Objective updates for Dragons, Baron, inhibitors, and tracked objective totals.

lol.live.kill_update

Kill total deltas so bots and dashboards can react without parsing the full state.

lol.live.tower_destroyed

Tower count deltas for match centers, alerts, and momentum panels.

lol.match.completed

Final match state so your app can reconcile live screens with post-game data.

Choose LoL on One Game Starter

Use One Game Starter when the product is League of Legends-only. It includes commercial use and LoL webhook access without paying for every game.

Create the webhook

Add your endpoint in the dashboard and subscribe to the exact LoL events your product needs.

Filter the stream

Use filters such as league, matchId, gameId, or side so your backend receives the updates it actually cares about.

Verify and dedupe

Use X-Cito-Signature to verify payloads and X-Cito-Event-Id as your idempotency key. Failed deliveries retry up to 3 times.

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.

View LoL Docs Endpoint Manifest Start Free

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.

Endpoint chain

Start with /api/v1/lol/matches/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.

GET

/api/v1/lol/matches/live

Today's matches, upcoming schedule, and live state.

Today's pro matches

/api/v1/lol/schedule/today

Today's pro matches fills in the detail around the primary response.

Upcoming matches

/api/v1/lol/schedule/upcoming

Upcoming matches fills in the detail around the primary response.

League schedule

/api/v1/lol/leagues/{leagueId}/schedule

League schedule fills in the detail around the primary response.

Returned data

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.

Best first request

Call /api/v1/lol/matches/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.

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.

Live API docs

Human-readable LoL endpoint reference

Postman collection

Import requests with variables

Endpoint manifest

Machine-readable endpoint list

Changelog

Recent API and data updates

Status

Operational status and uptime history

AI agent skill

Instructions for AI coding agents

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/matches/live. 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/analytics/drafts/{matchId}

Champion picks, bans, player roles, and side context.

GET

/api/v1/lol/live/{gameId}/visual-state

Live gold, score, objective, and game-time reads where available.

GET

/api/v1/lol/games/{gameId}/timeline

Timeline events, objective timings, and gold snapshots where available.

GET

/api/v1/lol/players/{playerId}/form

Sliding-window player performance over recent matches.

GET

/api/v1/lol/players/{playerId}/champion-pool

Champion picks and win rates over the requested match window.

GET

/api/v1/lol/matches/{matchId}/media

Live stream and replay links where available.

GET

/api/v1/lol/webhooks/events

Supported LoL webhook events for paid plans.

Use cases