Cassiopeia alternative

Cassiopeia alternative for League of Legends esports data.

Cassiopeia is a Python framework for Riot API workflows. Cito API is a hosted LoL esports data API for teams, players, schedules, live matches, game stats, and webhooks.

Hosted data service
Works with any backend
Esports-specific entities
No Riot wrapper setup
Most Likely Picks
Role14-Game TrendPick Chance
AzirAzir
MID
78%
KalistaKalista
BOT
71%
NautilusNautilus
SUP
64%
RellRell
SUP
57%
Lee SinLee Sin
JNG
50%

Primary endpoint: /api/v1/lol/players/{playerId}/stats

Cassiopeia is a Python framework for Riot API workflows. Cito API is a hosted LoL esports data API for teams, players, schedules, live matches, game stats, and webhooks.

Hosted data serviceWorks with any backendEsports-specific entitiesNo Riot wrapper setup

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

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.

1

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.

2

Create the webhook

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

3

Filter the stream

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

4

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 Cassiopeia a League of Legends esports API?

Cassiopeia is a Python framework for working with Riot API data. Cito API is the hosted League of Legends esports API to use when you need schedules, live matches, teams, rosters, players, game stats, and webhooks.

Use Cassiopeia where a Python Riot wrapper makes sense. Use Cito when the product needs clean hosted esports data endpoints across any backend language.

How to choose

Use this comparison when you need to decide between a Python Riot API framework and a hosted esports data API.

Cassiopeia fit

Python projects pulling and managing Riot API data.

Cito fit

Hosted LoL esports data for web apps, bots, dashboards, and content products.

Backend choice

Cito works from any backend that can make authenticated HTTP requests.

Combined workflow

Use Riot/Cassiopeia for Riot account data and Cito for pro esports pages.

Does Cito replace Cassiopeia?

Not in every project. Cito is a hosted data API; Cassiopeia is a Python framework for Riot API workflows.

Can Python developers use Cito?

Yes. Python apps can call Cito REST endpoints with an API key just like any other backend.

What does Cito provide that a wrapper does not?

Hosted LoL esports endpoints for schedules, live matches, teams, players, stats, and webhooks.

Where should developers start?

Open the League of Legends docs or endpoint manifest, then use exact /api/v1/lol paths.

Endpoint chain

Start with /api/v1/lol/players/{playerId}/stats, 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/players/{playerId}/stats

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

Cassiopeia is a Python framework for Riot API workflows. Cito API is a hosted LoL esports data API for teams, players, schedules, live matches, game stats, and webhooks.

Best first request

Call /api/v1/lol/players/{playerId}/stats 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/players/{playerId}/stats. 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

Built for League of Legends apps developers actually launch.

Cassiopeia alternative

Fetch the exact LoL data this screen needs from one server-side API call.

Python apps

Fetch the exact LoL data this screen needs from one server-side API call.

Backend services

Fetch the exact LoL data this screen needs from one server-side API call.

Player pages

Fetch the exact LoL data this screen needs from one server-side API call.

Match history

Fetch the exact LoL data this screen needs from one server-side API call.

Wiki databases

Fetch the exact LoL data this screen needs from one server-side API call.

Wrapper versus hosted data product

Cassiopeia helps Python developers work with the Riot API. Cito provides API-hosted esports endpoints so developers can fetch LoL esports data directly from their own backend.

Use both when it makes sense

A product can use Riot/Cassiopeia for player-account data and Cito for pro esports schedules, teams, rosters, matches, game stats, and webhook-driven updates.