LoL transfer API
LoL roster moves, player transfers, and org changes as API data.
Track who moved, where they went, when it happened, and which team or player page should update.
API response preview
Roster moves by player, team, and date
Useful endpoints
/api/v1/lol/transfersRecent transfers
/api/v1/lol/transfers/player/{playerId}Player moves
/api/v1/lol/transfers/team/{slug}Team moves
Run the request
X-API-Keycurl "https://api.citoapi.com/api/v1/lol/transfers" \ -H "X-API-Key: $CITO_API_KEY"
{
"transfers": [
{
"playerName": "Example",
"fromTeam": "old-team",
"toTeam": "new-team",
"date": "2026-05-10",
"type": "joined"
}
]
}Primary endpoint: /api/v1/lol/transfers
Track who moved, where they went, when it happened, and which team or player page should update.
Endpoint chain
Start with /api/v1/lol/transfers, 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/transfersRoster moves by player, team, and date.
Recent transfers
/api/v1/lol/transfersUse this first when the page needs roster moves by player, team, and date.
Player moves
/api/v1/lol/transfers/player/{playerId}Player moves fills in the detail around the primary response.
Team moves
/api/v1/lol/transfers/team/{slug}Team moves fills in the detail around the primary response.
Returned data
Track who moved, where they went, when it happened, and which team or player page should update.
Best first request
Call /api/v1/lol/transfers 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/transfers. 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.
Transfer trackers
Track player movement by team, player, date, and roster status.
Offseason hubs
Track roster moves in one place during the weeks when fans check daily.
Roster alert bots
Notify users when a player joins, leaves, or changes teams.
Org timelines
Show every known move for a team without rewriting historical pages.
Player profile history
Add team movement to a player profile beside stats, earnings, and match history.
Newsroom tools
Give writers a quick source for recent moves, old teams, and roster context.
Keep roster pages current
Use transfer rows to update team pages, player profiles, offseason trackers, roster alerts, and editorial tools without manually checking every org.
Query by team or player
Start from the full transfer feed, then drill into a single player or team when your UI needs a filtered timeline.
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.