GRID and Bayes alternative

GRID and Bayes LoL API alternative for developer apps.

GRID and Bayes are strong official-data options for enterprise and betting-grade workflows. Cito API is the self-serve LoL esports API for builders who need to launch fast.

Get Free API Key View LoL Docs

Self-serve testing

LoL app endpoints

No enterprise contract required to start

Developer-ready docs

API response preview

LoL API data for product pages, bots, and dashboards

JSON

Useful endpoints

/api/v1/lol/live

Live matches

/api/v1/lol/schedule/today

Today's schedule

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

Player stats

Run the request

X-API-Key

curl "https://api.citoapi.com/api/v1/lol/live" \
  -H "X-API-Key: $CITO_API_KEY"

{
  "success": true,
  "data": [],
  "meta": {
    "source": "Cito API",
    "game": "league-of-legends"
  }
}

Primary endpoint: /api/v1/lol/games/{gameId}/stats

GRID and Bayes are strong official-data options for enterprise and betting-grade workflows. Cito API is the self-serve LoL esports API for builders who need to launch fast.

Self-serve testingLoL app endpointsNo enterprise contract required to startDeveloper-ready docs

Quick recommendation

Should I use GRID, Bayes, or Cito API for League of Legends data?

Use GRID or Bayes when you need official enterprise or betting-grade League of Legends esports data. Use Cito API when you need a self-serve LoL esports API for developer apps, bots, dashboards, match centers, and content products.

Cito is the practical first test for small teams because the workflow is signup, docs, REST request, product build, then upgrade when usage grows.

View LoL Docs Endpoint Manifest Start Free

How to choose

Use this comparison when you need to separate official enterprise-data procurement from a self-serve developer API you can test today.

Official enterprise fit

GRID and Bayes for official commercial feeds, low-latency procurement, and betting-grade requirements.

Developer app fit

Cito for self-serve dashboards, Discord bots, wiki pages, match centers, and startup MVPs.

Buying motion

Cito supports free testing and low-cost paid plans; official enterprise feeds usually involve sales/procurement.

First Cito endpoints

/api/v1/lol/live, /api/v1/lol/schedule/today, /api/v1/lol/teams, /api/v1/lol/players.

Is Cito official Riot data?

No. Use GRID, Bayes, or Riot channels when official rights are required.

Why would a developer choose Cito first?

Cito is self-serve and built for getting a practical LoL esports app working quickly.

Can Cito be used for betting products?

Do not assume Cito is a betting-grade official data source. Evaluate rights, latency, compliance, and provider terms for betting use cases.

Can I switch later?

Yes. Many teams validate a product with a self-serve API, then add enterprise data procurement if the business requires it.

Endpoint chain

Start with /api/v1/lol/games/{gameId}/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/games/{gameId}/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

GRID and Bayes are strong official-data options for enterprise and betting-grade workflows. Cito API is the self-serve LoL esports API for builders who need to launch fast.

Best first request

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

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/games/{gameId}/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