lolpros.gg APIlolpros.gg ↗
Search pro League of Legends players, fetch regional ladder rankings, and retrieve full player profiles including accounts, teams, and social media via the lolpros.gg API.
curl -X GET 'https://api.parse.bot/scraper/f9ee2f0b-256c-4347-a14d-d8d546e7047e/search_players?name=faker' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for professional players by name and return their associated account details and ranks. Returns all accounts across matching player profiles.
| Param | Type | Description |
|---|---|---|
| namerequired | string | The name of the player to search for (e.g., 'caps', 'faker'). |
{
"type": "object",
"fields": {
"data": "array of account objects with accountName, current_rank, lp, wins, losses, last_played",
"status": "string, 'success'"
},
"sample": {
"data": [
{
"lp": 75,
"wins": 162,
"losses": 140,
"accountName": "Kajmak#289",
"last_played": "2026-05-05T14:25:19+00:00",
"current_rank": "Diamond 1"
},
{
"lp": 666,
"wins": 483,
"losses": 391,
"accountName": "J1HUIV#000",
"last_played": "2026-05-05T14:16:09+00:00",
"current_rank": "Grandmaster"
}
],
"status": "success"
}
}About the lolpros.gg API
The lolpros.gg API exposes 3 endpoints covering professional League of Legends player data: search by name, fetch regional ladder rankings, and retrieve full player profiles. The get_player_profile endpoint alone returns fields spanning accounts, social media handles, league history, and previous teams — all keyed by a player slug such as 'caps' or 'faker'.
Search and Player Lookup
The search_players endpoint accepts a player name string (e.g., 'faker', 'caps') and returns an array of account objects. Each object includes accountName, current_rank, lp, wins, losses, and last_played. A single search can return multiple accounts because pro players commonly maintain several ranked accounts.
Regional Ladder Rankings
The get_ladder endpoint returns the top 10 professional players ranked by score for a given region. The server parameter accepts region codes; 'EUW' and 'NA' are confirmed working values. Each ladder entry includes playerName, slug, country, position, score, team, and a primaryAccount object. Note that some regions may return an error if no ladder data is available for that server — build error handling around this before iterating across regions.
Full Player Profiles
The get_player_profile endpoint takes a slug (obtainable from search or ladder results) and returns a structured object with the player's name, country, position, score, a full accounts array, a social_media object, a leagues array, and a previous_teams array. This is the most detailed endpoint, giving historical team context alongside current competitive status.
- Look up all ranked accounts and current LP for a named pro player using search_players
- Build a regional leaderboard app showing the top 10 EUW or NA pros sorted by score
- Track win/loss records and rank changes across a pro player's multiple accounts
- Retrieve a player's previous teams and league history for a career timeline feature
- Cross-reference social media handles from get_player_profile to link to a player's external profiles
- Resolve player slugs from ladder data to feed into batch profile lookups via get_player_profile
- Monitor position and score fields across ladder calls to detect rank movement over time
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.