centrumsleja APIcentrumsleja.pl ↗
Query the SlayBet global leaderboard via the centrumsleja.pl API. Retrieve player rankings, balances, earned ranks, and season badges with optional username filtering.
What is the centrumsleja API?
The centrumsleja.pl API exposes 1 endpoint — search_ranks — that returns the SlayBet global leaderboard ranked by player balance. Each result includes up to 7 fields per entry: position, username, balance, earned ranks, and season badge. You can retrieve the full leaderboard or narrow results to specific players using a case-insensitive username substring filter.
curl -X GET 'https://api.parse.bot/scraper/63539564-5c66-4307-ac3d-441a6b09105c/search_ranks?query=garmor' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace centrumsleja-pl-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: SlayBet SDK — bounded, re-runnable; every call capped."""
from parse_apis.centrumsleja_pl_api import SlayBet, ParseError
client = SlayBet()
# Search for a specific user in the global leaderboard
for player in client.ranked_players.search(query="garmor", limit=3):
print(player.username, player.position, player.balance)
# Get full leaderboard, capped
try:
for player in client.ranked_players.search(limit=3):
print(player.username, player.position, player.balance, player.rank)
except ParseError as e:
print(f"error: {e.code}")
print("exercised: ranked_players.search")
Retrieve the SlayBet global leaderboard ranked by balance. Results include each player's position, balance, earned ranks, and season badge. When a query is provided, results are filtered to usernames containing the query (case-insensitive substring match). Without a query, the full leaderboard is returned.
| Param | Type | Description |
|---|---|---|
| query | string | Username substring filter (case-insensitive). Omitting returns the full leaderboard. |
{
"type": "object",
"fields": {
"total": "integer count of results returned",
"results": "array of ranked player entries"
},
"sample": {
"data": {
"total": 1,
"results": [
{
"rank": null,
"ranks": [],
"balance": "27138607415",
"position": 2,
"username": "garmor_",
"season_badge": null
}
]
},
"status": "success"
}
}About the centrumsleja API
What the API Returns
The search_ranks endpoint returns the SlayBet global leaderboard sorted by balance. The response contains a total integer indicating how many entries matched, and a results array where each element represents one ranked player. Player entries include their leaderboard position, current balance, earned ranks, and season badge — giving a snapshot of both current standing and historical achievement.
Filtering by Username
The optional query parameter accepts any string and performs a case-insensitive substring match against player usernames. Passing query=alex will return every player whose username contains "alex" regardless of capitalization. Omitting query entirely returns the full global leaderboard with no filtering applied.
Data Coverage and Freshness
The leaderboard reflects competitive standings across the SlayBet player base on centrumsleja.pl. The results array includes both rank position (useful for tracking movement) and season badge (useful for understanding a player's competitive history across seasons). There is no pagination parameter exposed; the endpoint returns all matching entries in a single response.
The centrumsleja API is a managed, monitored endpoint for centrumsleja.pl — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when centrumsleja.pl changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official centrumsleja.pl API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Track a specific player's leaderboard position and balance over time using the
queryfilter on their username. - Build a live leaderboard display showing top SlayBet players ranked by balance.
- Monitor season badge distribution across the top-ranked players to analyze competitive tier spread.
- Alert users when a queried username enters or exits a target rank range.
- Aggregate earned rank counts across the full leaderboard to identify rank milestones.
- Compare multiple player balances by issuing filtered
search_rankscalls for each username.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does centrumsleja.pl offer an official developer API?+
What does each entry in the `results` array include?+
results array includes the player's leaderboard position, username, current balance, earned ranks, and season badge. The total field at the top level tells you how many entries were returned for your query.Does the API expose individual match history or game-level statistics?+
Can I page through leaderboard results or set a result limit?+
search_ranks endpoint does not expose pagination or limit parameters. It returns all matching entries in a single response. If you need to segment results, you can fork this API on Parse and revise the endpoint to add offset and limit controls.How precise is the username filter — does it support exact match or wildcards?+
query parameter performs a case-insensitive substring match. It will return any username that contains the query string anywhere within it. Exact-match or regex-style filtering is not currently supported; the API covers substring matching only.