LoL player earnings API
LoL prize money, tournament payouts, and player earnings history.
Fetch career winnings, event counts, placements, payout rows, and earnings summaries for player profiles and leaderboards.
API response preview
Prize money and tournament payout history
Useful endpoints
/api/v1/lol/players/{playerId}/earningsTournament payouts
/api/v1/lol/players/{playerId}/earnings/summaryCareer totals
/api/v1/lol/leaderboards/earningsTop earners
Run the request
X-API-Keycurl "https://api.citoapi.com/api/v1/lol/players/{playerId}/earnings" \
-H "X-API-Key: $CITO_API_KEY"{
"playerId": "faker",
"totalEarnings": 1922084.56,
"events": 80,
"topResults": [
{ "event": "World Championship", "placement": 1, "earnings": 250000 }
]
}Primary endpoint: /api/v1/lol/players/{playerId}/earnings
Fetch career winnings, event counts, placements, payout rows, and earnings summaries for player profiles and leaderboards.
Endpoint chain
Start with /api/v1/lol/players/{playerId}/earnings, 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.
/api/v1/lol/players/{playerId}/earningsPrize money and tournament payout history.
Tournament payouts
/api/v1/lol/players/{playerId}/earningsUse this first when the page needs prize money and tournament payout history.
Career totals
/api/v1/lol/players/{playerId}/earnings/summaryCareer totals fills in the detail around the primary response.
Top earners
/api/v1/lol/leaderboards/earningsTop earners fills in the detail around the primary response.
Returned data
Fetch career winnings, event counts, placements, payout rows, and earnings summaries for player profiles and leaderboards.
Best first request
Call /api/v1/lol/players/{playerId}/earnings 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.
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.
| 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/players/{playerId}/earnings. Add supporting endpoints only when your page needs more context.
/api/v1/lol/players/{playerId}/earningsCareer prize pool earnings with tournament-by-tournament rows.
/api/v1/lol/players/{playerId}/earnings/summaryPlayer earnings totals, event counts, placements, and tracked history.
/api/v1/lol/players/{playerId}/teamsTeam history for org changes, roles, and date ranges.
/api/v1/lol/teams/{slug}/roster/historyHistorical rosters with roster membership periods.
/api/v1/lol/transfersRecent transfer activity across tracked LoL teams and players.
/api/v1/lol/teams/{slug}/earningsOrganization-level earnings and tournament results where tracked.
/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/games/{gameId}/statsGame-level player stats after source publication.
/api/v1/lol/webhooks/eventsSupported LoL webhook events for paid plans.
Use cases
Built for League of Legends apps developers actually launch.
Earnings leaderboards
Rank players by tracked career winnings and tournament payouts.
Player profile pages
Fetch the exact LoL data this screen needs from one server-side API call.
Fantasy research
Compare prize history, recent form, champion pool, and match context before building projections.
Content pages
Add concrete earnings and tournament rows to player rankings, profiles, and event previews.
Scouting dashboards
Compare teams by match history, objective control, champion pool, and roster movement.
Sponsor research
Find high-profile players and orgs with public prize history and tournament context.
Add prize money to player pages
Show career earnings, tournament payouts, placements, and event counts beside player stats, teams, champion pools, and match history.
Build rankings without spreadsheets
Use earnings endpoints for top earner pages, player comparisons, sponsor research, and historical content around major events.
Pricing
Start free. Upgrade when your LoL product needs room to grow.
Free testing includes 500 requests/month. Starter handles early products at $25/month. Builder is the $50/month tier for earnings, org history, transfers, webhooks, and higher-volume LoL apps.