Riot API vs Cito API

Riot API vs Cito API: what each one is built for.

Riot API is the source for summoner, account, and ranked data. Cito API is built for pro esports products that need schedules, live matches, teams, rosters, player earnings, transfer history, and webhooks.

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

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

Start with the screen's main state, then add roster, stats, or webhook rows only when needed.

Live data layer

Match center signal stack

REST JSON

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 request

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

Riot API vs Cito API workflow comparison.

Primary endpoint

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

Pro esports schedules and live matches

Player earnings and org history

Roster history and transfer tracking

Self-serve, no sales call required

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

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 webhook

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

Filter stream

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

Verify delivery

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

Riot API vs Cito API: which should I use for a League of Legends app?

Use Riot API for summoner, account, ranked, and champion mastery workflows. Use Cito API when the product needs pro esports schedules, live matches, player earnings, team rosters, org history, transfers, and webhooks.

The two APIs solve different jobs. Riot's developer endpoints are built for game-client and account-linked workflows. Cito is built for the pro esports product layer that Riot does not package for direct developer use.

View LoL Docs Endpoint Manifest Start Free

How to choose

Use this comparison when you are planning a League of Legends app and need to decide which API to wire up for which data type.

Riot API fit

Summoner lookup, PUUID, ranked ladder, champion mastery, match history tied to a player account.

Cito API fit

Pro schedules, live matches, team rosters, player earnings, org history, transfer tracking, and webhooks.

Overlap

Minimal. The two APIs serve different parts of the LoL data ecosystem.

Combined use

Many apps use Riot for account data and Cito for the pro esports layer. They complement each other.

Does Cito replace Riot API?

No. Cito is a complement for the pro esports layer. Use Riot for account and ranked workflows.

Does Riot API have player earnings or org history?

No. Those are Cito-specific endpoints not available through Riot's developer products.

Can I use both APIs in the same app?

Yes. Use Riot for summoner and account data and Cito for pro schedules, teams, earnings, and live match state.

Do I need a Riot API key to use Cito?

No. Cito provides its own API access. Sign up for a Cito API key independently.

Endpoint chain

Start with /api/v1/lol/live/{gameId}/visual-state, 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/live/{gameId}/visual-state

Riot API vs Cito API workflow comparison.

Live pro esports matches

/api/v1/lol/live

Live pro esports matches fills in the detail around the primary response.

Career prize earnings

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

Career prize earnings fills in the detail around the primary response.

Full roster history

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

Full roster history fills in the detail around the primary response.

Returned data

Best first request

Call /api/v1/lol/live/{gameId}/visual-state 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.

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.

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/live/{gameId}/visual-state. 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.

Built for League of Legends apps developers actually launch.

Side-by-side API comparison

Show what Riot API and Cito API each cover so developers pick the right tool.

Choosing the right LoL API

Help developers decide between Riot, Cito, PandaScore, and other options.

Filling Riot API gaps

Add pro esports data, earnings, and roster history that Riot does not package.

Esports app planning

Plan which endpoints to call before writing integration code.

API evaluation

Test endpoint responses and confirm data coverage before committing to an integration.

Developer research

Compare LoL API options by coverage, pricing, and developer experience.

Use Riot where it is the right fit

Riot API is built for account-linked workflows: summoner lookup, PUUID resolution, ranked ladder, champion mastery, and match history tied to a player account. Those endpoints are the right tool for those jobs.

Use Cito for pro esports product data

Cito is the API to reach for when the product needs pro team rosters, player earnings history, org transfers, scheduled esports matches, live game state, near-live gold and objective monitoring, and webhook delivery. Riot does not package those workflows for direct developer consumption.

Pricing

Start free. Upgrade when your LoL product needs room to grow.

Free testing includes 500 requests/month. One Game Starter starts at $10/month for a focused LoL product with commercial use and LoL webhooks. Pro is the $50/month tier for higher-volume apps across every game.

Free

500 requests/month for endpoint testing.

One Game Starter

$10+/mo

LoL-only access, webhooks, commercial use, and 10k-250k requests/month.

Pro

$50/mo

All games, higher limits, webhooks, earnings, org history, and production room.

Riot API vs Cito API: what each one is built for.

Match center signal stack

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

Gold swing webhook

Choose LoL

Create webhook

Filter stream

Verify delivery

Riot API vs Cito API: which should I use for a League of Legends app?

How to choose

Does Cito replace Riot API?

Does Riot API have player earnings or org history?

Can I use both APIs in the same app?

Do I need a Riot API key to use Cito?

Start with /api/v1/lol/live/{gameId}/visual-state, then add the supporting rows your screen needs.

Live pro esports matches

Career prize earnings

Full roster history

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

Pro Esports API

Ranked and Ladder Workflows

Docs, examples, and machine-readable endpoint files.

Endpoint paths for this workflow.

Built for League of Legends apps developers actually launch.

Side-by-side API comparison

Choosing the right LoL API

Filling Riot API gaps

Esports app planning

API evaluation

Developer research

Use Riot where it is the right fit

Use Cito for pro esports product data

Start free. Upgrade when your LoL product needs room to grow.

People also ask before choosing a LoL API.

What is the best LoL Esports API?

What is the best LoL API Endpoints?

What is the best League of Legends API?

What is the best LoL Schedule API?

What is the best LoL Match Stats API?

What is the best LoL Live Score API?